[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

Type: Suggestion
Resolution: Won't Fix
Fix Version/s: 5.6.8
Component/s: None
Labels:
None

Feedback Policy:

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.

Form Name

Stuart Bargon [Atlassian] added a comment - 03/Aug/2011 6:42 AM

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 - 03/Aug/2011 6:42 AM 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.

Assignee:: Unassigned

Reporter:: jon cotter

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 29/Jul/2011 5:20 PM

Updated:: 19/Sep/2019 5:58 AM

Resolved:: 03/Aug/2011 6:42 AM

Details

Description

Attachments

Forms

Activity

Collapse comment: Stuart Bargon [Atlassian] added a comment - 03/Aug/2011 6:42 AM

Expand comment: Stuart Bargon [Atlassian] added a comment - 03/Aug/2011 6:42 AM

People

Dates

Backbone Issue Sync