Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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 separate Backlog status from sprint board?

I have a custom workflow that has issues created in the backlog and then transitioning to To Do for the sprint board. However, the only way to have Backlog items show in the Scrum Backlog is to map that status to the To Do column of the board. If I move the Backlog status to unmapped, everything disappears from the Backlog screen and there is no dedicated "Backlog" column like there is in the Kanban template. So I have two questions:

1. Is there a way to have backlog items visible in scrum backlog WITHOUT having to map the status to one of the active board columns?

2. If not, how can I make issues auto-transition from Backlog to To Do when the sprint is started? 

2 answers

1 accepted

0 votes
Answer accepted

Hi @Amber Arguijo,

You are right about the columns. The backlog and work actively being worked on is managed by assigning items to sprints. And it is the sheer action of starting a sprint that pulls issues in the active sprint view.

If you have a formal process in place for elaborating issues before they end up on the sprint planning, it is not uncommon to have this preparation process managed through a separate (kanban) board, where you move issues through the preparation steps, ending in to do. If you exclude the steps before to do using the board filter of your scrum board, only items ready to be worked on will be on the board.

That may indeed be overkill for your situation, so automating a status transition when a sprint starts is definitely possible as well. Have a look at this sample rule from the template library, where all issues in the starting sprint are updated.

The only thing you should do differently is pick the transition issue action instead of editing the issues, the action configured in that sample rule.

Hope this helps! 

Hello @Amber Arguijo 

Are you working with a Team Managed project or a Company Managed project?

Company Managed, and I have Jira Admin permissions.

In that case I concur with @Walter Buggenhout _ACA IT_ 's suggestions. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

308 views 9 7
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