• 36
    • 21
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding suggestion.

      Sprint field displays 'None' on view issue and issue navigator when an issue is only in completed sprints

      Steps to Reproduce

      • Create a sprint, with issues from the board backlog
      • Complete the sprint

      Results

      • The sprint field value is displayed as 'none' for all the issues in the completed sprint, as long as the issue belongs to no other active sprint.

      Symptoms
      If you search for issues using the JQL below:

      Sprint is not empty
      

      There are results displayed with Sprint = None:

      If we open one of such issues, we can see that although the field Sprint is None, the Agile section displays that the issue belonged to a sprint which was completed:

      Expected result:
      The sprint field should display the sprint in which the issue was included.

            [JSWCLOUD-10460] Sprint field showing 'None' causes confusion

            Ian Morris added a comment -

            Also seeing this issue. Definitely causing confusion, and adds difficulty to querying the information I need when planning future work.

            Ian Morris added a comment - Also seeing this issue. Definitely causing confusion, and adds difficulty to querying the information I need when planning future work.

            a 10 years bug and still confusing the calculation

            Refan Andros added a comment - a 10 years bug and still confusing the calculation

            Ryan Coles added a comment -

            This is causing problems for us as well. Has anyone found a workaround? 

            Ryan Coles added a comment - This is causing problems for us as well. Has anyone found a workaround? 

            This is actually a bug as it has caused issues with other products of Atlassian like Jira Align. What we are finding is that when "None" shows up on the ticket in Jira, Jira Align for some reason pushes the ticket into the next available open sprint. This has caused future sprints velocity to spike and we don't know how to get rid of the "None" in the ticket in Jira. You have to understand that stories can be moved from sprint to sprint for whatever reasons. This "None" that appears in the sprint field needs to be fixed so it doesn't show and cause further issues.

            James Wicks added a comment - This is actually a bug as it has caused issues with other products of Atlassian like Jira Align. What we are finding is that when "None" shows up on the ticket in Jira, Jira Align for some reason pushes the ticket into the next available open sprint. This has caused future sprints velocity to spike and we don't know how to get rid of the "None" in the ticket in Jira. You have to understand that stories can be moved from sprint to sprint for whatever reasons. This "None" that appears in the sprint field needs to be fixed so it doesn't show and cause further issues.

            Shane Larkin added a comment - - edited

            This is causing me problems too.This issue seems to have been on the backlog since 2014!!

            What makes it even worse seems to be the API works differently, so if I run a JQL query and then do the same with an API call I get different results.

            Shane Larkin added a comment - - edited This is causing me problems too.This issue seems to have been on the backlog since 2014!! What makes it even worse seems to be the API works differently, so if I run a JQL query and then do the same with an API call I get different results.

            This is really confusing, please revert to diplaying the completed sprint(s) in this field. Even "+1" button does not help and it makes me do unnecessary actions by clicking on it.

            denis.kochergin added a comment - This is really confusing, please revert to diplaying the completed sprint(s) in this field. Even "+1" button does not help and it makes me do unnecessary actions by clicking on it.

            Please refer to this article: Sprint field is showing none:
             

            When an issue is not completed during a sprint, but the sprint is closed, it will show as none (but then also have a +1 to show it was in that closed sprint)

            Would the watchers of this issue be ok with me reopening it and changing the title to "Sprint field showing 'None' causes confusion"

            Anusha Rutnam added a comment - Please refer to this article: Sprint field is showing none :   When an issue is not completed during a sprint, but the sprint is closed, it will show as none (but then also have a +1 to show it was in that closed sprint) Would the watchers of this issue be ok with me reopening it and changing the title to "Sprint field showing 'None' causes confusion"

            Has this truly been resolved as I am seeing this issue currently on an issue within JIRA?

            Edmund Hardy added a comment - Has this truly been resolved as I am seeing this issue currently on an issue within JIRA?

            This is also affecting a project I'm helping to manage. A lot of issues that were in completed sprints have shown up in the backlog having a sprint of "None +1". I didn't understand what was causing this, so I tried to clean them up by adding them to a new sprint that could be closed — but this just made things worse.

            GavinAnderegg added a comment - This is also affecting a project I'm helping to manage. A lot of issues that were in completed sprints have shown up in the backlog having a sprint of "None +1". I didn't understand what was causing this, so I tried to clean them up by adding them to a new sprint that could be closed — but this just made things worse.

            Same problem, creating all kinds of reporting problems (+1)

            Roosevelt Washington added a comment - Same problem, creating all kinds of reporting problems (+1)

              pteen pat (Inactive)
              dconrad Danilo Conrad
              Votes:
              43 Vote for this issue
              Watchers:
              49 Start watching this issue

                Created:
                Updated: