Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1828

action-based permissions

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Draft (View Workflow)
    • Priority: P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Back End Estimate:
      XXL < 30 days
    • Development Team:
      Core: Platform
    • Calculated Total Rank:
      27
    • PO Rank:
      105
    • PO Ranking Note:
      CB: Bumping this way up so it is ranked similarly to the user-facing features that require it (see links below)
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R4
    • Rank: GBV (MVP Sum 2020):
      R4
    • Rank: hbz (TBD):
      R4
    • Rank: Lehigh (MVP Summer 2020):
      R4
    • Rank: MO State (MVP June 2020):
      R2
    • Rank: U of AL (MVP Oct 2020):
      R2

      Description

      Quite a few of the new permissions describe a specific action, e.g. change due date (UIU-582) or cancel a request (UIREQ-110).

      The backend APIs currently have permissions to allow a user to either edit (replace) a record or not.

      In order for specific actions to be associated with specific permissions we need to decide upon a general approach to how we model (name of permission, how is it described in the API and how we describe what action it relates to).

      3-17-2021: Since this jira has been created, the practice in the community has been more hands off with these kinds of technical decisions, with the idea being that a team with capacity can explore a requirement and propose a technical solution that could meet their needs and then be considered by other teams as requirements in their areas. This seems to be what is happening with permissions in this area, and there are explorations happening with things like permission overrides that are related to this need. Accordingly, the features that were blocked by this jira have been unblocked to make it easier to see that development on those features can and should proceed based on team and subject area priorities and capacity - Erin Nettifee

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                jakub Jakub Skoczen
                Reporter:
                marcjohnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases