Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to show past sprint issues that have not yet gone into production

Hi. I am not a Jira Admin - just a Project Admin (and Project Lead) - and also new to Jira.

Our team works to two-week development sprints.  Our sprint board contains the following columns: To Do, Analysis, Development, QA and Done. All issues are planned for a single sprint ahead of time, and at the end of the two weeks, all issues would hopefully have been moved to the "done" status and the sprint is closed.  

However, just because we have finished our development, it does not necessarily mean our work has been released to a production environment. It could be another two, three or even more weeks until an issue is required to be pushed live. (We are responsible for promoting issues to production as well as developing them)

Our stake-holders now want to be able to see a list of all issues which have been completed as far as development is concerned, but not yet pushed to production. What is the best way to set this up? I thought about just adding another swimlane to our board - maybe something like "Development Complete" and place that just before the "Done" column. But if I did that, as each sprint closes, I would have to move un-released issues from the current sprint to the next - and maybe even to the one after that. This is messy, but would mess up our reporting.

Is there a better solution?

Thanks

1 answer

1 accepted

2 votes
Answer accepted

Yes, you should add the new status you mentioned but organize your board to display both statuses in the last column. That way both statuses will be treated as completed from the sprint perspective. However, you will be able to search for the issues based on their status.

An example board configuration:

Screenshot from 2019-12-13 15-40-30.png

Like Vijay Shanmugam likes this

Thanks for the response.  So when I close down a sprint, tasks with a status of "Development Complete" will be removed from the backlog, but will still show up in the search results. Is that correct? (I only have a production instance of Jira so cannot close a sprint to test this)

 

If so, that is exactly what I want.

The tasks are removed from the backlog as soon as you put them in the sprint.

 

You can always experiment within a new separate project.

Just tried it out. It works perfectly. Thanks for your support

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Opsgenie

Opsgenie and Amazon team up to launch new DevOps Guru integration - now available!

We’re proud to announce that our integration with Amazon DevOps Guru is now live. The Amazon and Opsgenie product teams have worked together to build a deep integration between Opsgenie and the new...

283 views 0 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you