Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

(SCRUM) Cannot see new tickets ticket types in backlog while excluding from Active Sprint Board

Scott Buratt
Contributor
July 21, 2022

New (company defined) SCRUM Jira Project.

  1. Created new issue types but they do not show up on the backlog
  2. Do not want these new issue types to show up in the Active Sprint Columns

I'm sure there's a way but it's not clear how.

2 answers

2 accepted

0 votes
Answer accepted
Scott Buratt
Contributor
July 22, 2022

Hi again @Trudy Claspill 

With a good nights sleep and your some of your queries, I figured out what the issue was.

Simply, add the ticket states within a Board Column but just don't add the ticket to a Sprint.

Thanks again :-)

...Scott

0 votes
Answer accepted
Trudy Claspill
Community Champion
July 21, 2022

Hello Scott,

After creating your new issue types, did you add them to the Issue Type Scheme associated with the project? 

Are the new issue types Standard issue types or Subtask issue types?

What is the filter for board?

Are you saying you want the new issue types to show up in the backlog screen, but you don't want those issues to show up in the board view when you are looking at Active Sprints? Do you plan to assign them to sprints that will be started?

Your board will show the same issues in the sprint that you see in that sprint when looking at the Backlog. The filter for the board determines which issues will fundamentally be available for display in both the Backlog and Active Sprints board view. You would have to add a Quick Filter to the board and use that when viewing the Active Sprints board view to exclude those issues you don't want to see.

Can you provide more information about your use case? What are you trying to accomplish? That will help us provide you with better feedback.

Scott Buratt
Contributor
July 22, 2022

Hi @Trudy Claspill 

I must have lost my mind yesterday in defining the actual issue.

l'm going to close this one down and open a new one but the actual issue is

Created new Issue "States"

The new Issues States are not showing up in the Backlog but do not want these new Issue States to show up in an Active Sprint Board.

Perhaps some of your questions may be pertinent so, I'll provide the answers here

  • After creating your new issue types, did you add them to the Issue Type Scheme associated with the project?
    • I did create some new issue types and they are in the "scheme" for this project
  • Are the new issue types Standard issue types or Subtask issue types?
    • New issue types are not subtasks types
  • What is the filter for board?
    • The filter does see all issue types AND can see the newly introduced "States"
  • Are you saying you want the new issue types to show up in the backlog screen, but you don't want those issues to show up in the board view when you are looking at Active Sprints? Do you plan to assign them to sprints that will be started?
    • The new States should show up in the backlog but shouldn't show up as columns within the Active Sprint Board (they will not be added to a sprint)
  • Your board will show the same issues in the sprint that you see in that sprint when looking at the Backlog. The filter for the board determines which issues will fundamentally be available for display in both the Backlog and Active Sprints board view. You would have to add a Quick Filter to the board and use that when viewing the Active Sprints board view to exclude those issues you don't want to see.
    • I am looking to exclude the new states from the Active Sprint Board (as they will never be in the sprint), At the prior company I was in, they had this same model
  • Can you provide more information about your use case? What are you trying to accomplish? That will help us provide you with better feedback.
    • The new "states" will be defined for the Product Team to create and refine stories prior to any developer needing to be engaged. Once the ticket is reviewed by the team, then the ticket state will be ready to add to a sprint (when appropriate)

Thanks again and sorry for the initial (missed( definition of the problem

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events