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

[JIRAALIGN-1220] Developer Team Role Can't Modify Acceptance Criteria When Story Is In Unassigned Backlog

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 10.68
    • 10.65
    • team - stories
    • None
    • 1
    • Severity 3 - Minor
    • Dementors - RHP8

      Issue Summary

      Developers should be able to modify the acceptance criteria and add acceptance criteria if stories aren't in an in-progress sprint.

      Ideally, a developer should be able to update the acceptance criteria in the unassigned backlog without being the story owner/assignee. Once the story has been planned and is allocated in an "Active" sprint then the application should lock the acceptance criteria to prevent a developer from modifying the scope once the sprint is in progress.

      Steps to Reproduce

      1. Step 1 - Navigate to the unsigned backlog for the team stories
      2. Step 2 - As a developer (team role) System role (team member) try to modify the acceptance criteria of a story not owned.
      3. Step 3 - Assign the story to the developer and then save
      4. Step 4 - Modify the acceptance Criteria

      Expected Results

      All team roles except Stakeholder should have access to modify the acceptance criteria anytime the story isn't in progress on an active sprint/in progress sprit.

      Actual Results

      Developers can't modify acceptance criteria unless they. are assigned to the story see the internal GSAC ticket tied to this defect for screenshots.

      Workaround

      Developers have to assign the stories to themselves

            kbyrd@atlassian.com Kyle Byrd (Inactive)
            ddortch@atlassian.com Darryl Dortch (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: