Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-3484

As a Project Lead I would like to be able to Lock down a version after a sprint has started so that others cannot add additional work

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • 5.6.8
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      It would be useful if I could lock a version once it has started so that no one can add tickets into that version (except me). This would help me police against those who add work to the current sprint accidentally or not. Often people unknowingly drop tickets into the current sprint, and right now the only way to stop this is to be vigilant about checking email notifications.

            [JSWSERVER-3484] As a Project Lead I would like to be able to Lock down a version after a sprint has started so that others cannot add additional work

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3065799 ] New: JAC Suggestion Workflow 3 [ 3660929 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2624311 ] New: JAC Suggestion Workflow [ 3065799 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2326022 ] New: Confluence Workflow - Public Facing v4 [ 2624311 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2042921 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2326022 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2030999 ] New: JIRA PM Feature Request Workflow v2 [ 2042921 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 738287 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2030999 ]
            Martin (Inactive) made changes -
            Backlog Order (Obsolete) Original: 5030000000
            Workflow Original: GreenHopper Kanban Workflow v2 [ 339580 ] New: JIRA PM Feature Request Workflow v2 [ 738287 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Stuart Bargon [Atlassian] made changes -
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Stuart Bargon [Atlassian] made changes -
            Fix Version/s New: 5.6.8 [ 18798 ]
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Stuart Bargon [Atlassian] added a comment -

            Hi Jon,
            We have no plans to implement this feature, however you might be able to get the desired behaviour by using the workflow in JIRA. If you have any issues designing your workflow please contact support, they would be happy to help to you.

            Stuart Bargon [Atlassian] added a comment - Hi Jon, We have no plans to implement this feature, however you might be able to get the desired behaviour by using the workflow in JIRA. If you have any issues designing your workflow please contact support, they would be happy to help to you.

              Unassigned Unassigned
              5ec46adde265 jon cotter
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: