Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

moving of an issue to a previously released version / sprint

Craig Jonathan
Craig Jonathan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
March 21, 2012

A common situation is in a product/project with many issues is that some issues will be indirectely fixed in a previous release - though not testet at the time. It would therefore be more correct to move the issues as resolved/closed in a previous released release/sprint instead of keeping them in the current release/sprint.

Kan Jira/Greenhopper acomodate this (preferably without un-releasing a released release if possible).

Thanks!!

Answer
Watch
Like Be the first to like this
287 views

1 answer

1 accepted

0 votes
Answer accepted
Björn Wennerstr
Björn Wennerström March 27, 2012

Up until GH 5.8 both sprints and releases are stored in fixVersion. GH 5.9 seems to introduce a separate field for sprints. Either way, just make the field(s) visible on the appropriate screens and change the value by editing the issue.

View More Comments
Craig Jonathan
Craig Jonathan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
April 2, 2012

takk for svaret :)

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events