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

An issue appears both in the current and next sprint. How can that be? Is it a bug or wrong usage?

Hi all,

 

An issue appears both in the current and next sprint. How can that be? Is it a bug or wrong usage? Also when I use this query "Sprint = 15 and Sprint = 16 order by created DESC", it returns that item that is present in both sprints.

How come? Did anyone experience the same or something similar?

 

Thanks & best regards,

Robert

1 answer

0 votes

Hello @Robert Masur

Sprints are an interesting part of issue history. An issue can be in several sprints at the same time from the JQL point of view given they maintain history from previous sprints.

This is to say, if an issue was part of an old sprint and then was take to the next one and so on, when searched through JQL 'Sprint =' you will find it matches all of them.

It is interesting though that you mention it matches the current sprint and the next one that is indeed odd. Can you give more details on the sprint setup you have?

Hi @Fernando Bordallo 

 

Thanks for your response. I understand that previous/historic sprints should be displayed and stored for an issue. 

But in my case, the issue was actually assigned to the current sprint and the next sprint which hasn't been started at the time. That problem occurred only on a single issue and I could resolve it by:

1. Going to the backlog view

2. drag the issue from the next sprint to the current sprint

3. reloading the backlog view.

Since then the issue is only displayed in the current sprint. That problem did not occur anymore.

To answer your question re the sprint setup: It's a next gen project. So there is not much I could setup to my knowledge. I usually have two to three sprints created ahead of the current sprint. Each sprint has a custom duration of three weeks.

 

Best regards,

Robert

Like Fernando Bordallo likes this

Hello @Robert Masur

Thanks for leaving this comment clarifying your scenario for future reference 🚀Glad you resolved it

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Next-gen

Keyboard shortcuts have arrived for next-gen projects!

...ollected feedback from users around the lack of shortcuts, and we’re here to address that: In next-gen projects, I miss the keyboard shortcuts badly. This is particularly true on the Board, but also i...

5,198 views 5 14
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