Uploaded image for project: 'SR for Jira - Development'
  1. SR for Jira - Development
  2. SRJIRA-3121

Read-only behaviour with exception condition doesn't reliably work on user picker field edits

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Done
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 5.4.43
    • Fix Version/s: None
    • Component/s: Behaviours
    • Labels:
      None
    • Critical Points:
      1

      Description

      This is a follow-up issue to SRJIRA-3084.

      Conditional Behaviours that deal with User Picker fields have been observed to not work correctly when switching between users who have access to edit a field and those that do not have access.

      First tested with the condition: "Except: Current user is current assignee."

      Steps to reproduce:

      1. Create a Behaviour to make a field (tested with Fix Version/s) readonly and add the condition "Except: Current user is current assignee". Map said behaviour to a test project.
      2. Create an issue. The assignee is "Unassigned" and the field should be readonly as expected.
      3. Assign the issue to yourself (current user)- the field should be writable, as expected.
      4. Assign the issue to another user (or make it unassigned again). The field should be readonly, but it is still writable. The browser console will re-display a message like [SR Behaviours] Behaviours not applicable to the current form / screen.
      5. Refresh the page. The field is now correctly readonly and it the edit popup form is enabled

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jcarter Jonny Carter
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: