Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-4764

Epic permission is not being correctly evaluated/respected.



    • 1
    • Severity 2 - Major
    • No


      Issue Summary

      Epic permission is not being correctly evaluated/respected for Custom Hierarchies

      If we remove all the permissions from the Epic, and only leave the view permission for it, we can't save any changes, as the save button is not present, and just when we click on Save the POST call is made to update the details.

      Now, on the Custom Hierarchies, it is behaving in a different way, as once we select a value, a POST call is immediately made, saving the changes on it and ignoring the permission for that item.

      Steps to Reproduce

      1. User is mapped to "TestRole".
      2. Go to Administration > Roles > Select "TestRole"
      3. Expand Administration -> Other Setup ->Click on Manage next to "Custom Hierarchies"
      4. Disable Edit option for all the Custom Hierarchies available and enable only view option
      5. Expand Portfolio > Epics and enable only "Epic Detail Report" option and disable all the other options
      6. Login to the user mapped to "TestRole"
      7. Go to Portfolio > Epics and open any Epic from the grid
      8. Save button is not visible
      9. Now from custom hierarchy dropdown, we are able to change the Custom hierarchy mapped to the drop-down

      Expected Results

      If Edit permission is not allowed for Epics, then there should not be any POST call for custom hierachies.

      Actual Results

      Even for Epic view permission, we are able to change the Custom Hierarchies of an Epic.


      Currently there is no known workaround for this behavior. A workaround will be added here when available


        Issue Links



              dfuller@atlassian.com Don Fuller
              37857daa0c44 Mangala Narayana
              6 Vote for this issue
              12 Start watching this issue



                Backbone Issue Sync