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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,866
Community Members
 
Community Events
184
Community Groups

Why is issue not appearing in sprint when I create it using the create button under the sprint group

Issue appears in the sprint when I create it using the create button at the top of the page, but does not appear in the sprint when I create and issue using the button at the bottom of the sprint group.

Will have to check what version our Jira is. 

3 answers

1 vote
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 24, 2022

Welcome to the Atlassian Community!

Generally, you should not be creating issues straight into an active sprint (or even a future one).  As work arrives, it should go into the backlog, get refined, and then be compared with the rest of the backlog when the team are selecting what needs to go into the next sprint.

Is that not what you are doing? I have to ask why are you trying to create issues directly in a sprint?  What is the reason for doing it?

(Your version of Jira doesn't matter for this question, you've said "Cloud" in the tags, so we know it's "latest")

The project was set up as a sprint when it should be kanban.  Also, it doesn't make sense that one button creates it directly into the sprint and one button doesn't.  

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 27, 2022

When you use "create issue" in general, it will only put an issue into a sprint if you explicitly fill in the sprint field during creation.  The buttons are not doing the sprint allocations, you are.

Yes, I put filled up the sprint field in both situations  What now?

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 30, 2022

I don't know what you are looking for next. You are selection a sprint as you create the issue

We're having the same issue for several months now.  Adding a card to a future sprint used to work fine, but now the card is always added to the bottom of the backlog and we have to drag it to the correct sprint.  (Please assume we have a good reason for using this feature that used to work.)

2023-05-24_09-30-13.png

If you create the ticket from the sprint, make sure that you are adding the created issue in the current active sprint by selecting the appropriate value in sprint field drop down. If you don't select the sprint, issue will go and sit in backlog.

It is added to the sprint when I created it.  It didn't appear in either the backlog or the sprint.

Suggest an answer

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

Atlassian Community Events