Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    JSWCLOUD-20553Display Project creation date
  2. Suggestion
    JSWCLOUD-20699Configure the Sprint Health Gadget colors based on the issue status
  3. Suggestion
    JSWCLOUD-25674Allow additional custom fields for Releases/Versions
  4. Suggestion
    JSWCLOUD-26380Change "Target start" and "Target end" fields created by Advanced Roadmaps into regular Jira date time type fields
  5. Suggestion
    JSWCLOUD-26667Add a Smart Value for Calculating Business Hours in Jira Cloud
  6. Suggestion
    JSWCLOUD-27784Add the ability to present the Epic status on the board timeline view
  7. Suggestion
    JSWCLOUD-12717Show Epic progress on Cards in Board
  8. Suggestion
    JSWCLOUD-22261Support Build Integration between Jira Cloud and Google Cloud Build
  9. Suggestion
    JSWCLOUD-24167Project Resolution Scheme
  10. Suggestion
    JSWCLOUD-26564Advanced Roadmaps - Add support for more custom fields
  11. Suggestion
    JSWCLOUD-9929As a Product Owner I want to split an epic easily
  12. Suggestion
    JSWCLOUD-15276Simplified Workflow: add option to disable the creation of new statuses
  13. Suggestion
    JSWCLOUD-20774Notification for people fields in Team-Managed
  14. Suggestion
    JSWCLOUD-25865Advanced Roadmap macro should allow "read-only" permissions for non licensed Jira users.
  15. Suggestion
    JSWCLOUD-9009As Product Owner I want to assign Epics (with all its stories) to a Version
  16. Suggestion
    JSWCLOUD-16390Public REST API for completed sprint Velocity (both committed and completed)
  17. Suggestion
    JSWCLOUD-10460Sprint field showing 'None' causes confusion
  18. Suggestion
    JSWCLOUD-16160Ability to change text color in body of CODE or PANEL block
  19. Suggestion
    JSWCLOUD-23516Ability to sort project grouping in advanced roadmap.
  20. Suggestion
    JSWCLOUD-27302Support for Assets field in Jira Plan
  21. Suggestion
    JSWCLOUD-4917Allow Column Constraint to be set to any numeric field (i.e Story Points)
  22. Suggestion
    JSWCLOUD-25421DevOps Automation: When project scope is multiple projects, the Automation does not allow the option *Same project* or *Same project as trigger* when creating a version
  23. Suggestion
    JSWCLOUD-6911As a user, I'd like current sprint issues to be ranked higher than backlog issues
  24. Suggestion
    JSWCLOUD-8095Allow user to configure Quick Filters that provide dynamic filtering by value for a particular field
  25. Suggestion
    JSWCLOUD-16588When closing a sprint via the REST API, you should be able to indicate where to place the incomplete issues in the sprint
  26. Suggestion
    JSWCLOUD-18142Ability to drag drop Sprint buckets on the Backlog View
  27. Suggestion
    JSWCLOUD-24212Support for Related Work when managing Releases via Automation
  28. Suggestion
    JSWCLOUD-26132Board WIP limit numbers not visible (Constraint numbers) on the Enhanced board
  29. Suggestion
    JSWCLOUD-16316Allow associating JIRA Software board with business/service desk project type
  30. Suggestion
    JSWCLOUD-24504Be able to use Smart Value for a Custom Field Default Value
  31. Suggestion
    JSWCLOUD-27779Add a validation for "Target start" and "Target end" in Timelines
  32. Suggestion
    JSWCLOUD-692Set ranking values based on current sort order
  33. Suggestion
    JSWCLOUD-9621Report - Provide chart for Cycle / Lead Time Distribution
  34. Suggestion
    JSWCLOUD-9806Better/More options regarding Sprint notifications within JIRA Software
  35. Suggestion
    JSWCLOUD-14934Branch information missing from the list of commits in the Development panel
  36. Suggestion
    JSWCLOUD-9631Enhancement Request: Add a moving average line to the Velocity Chart
  37. Suggestion
    JSWCLOUD-18689Allow JIRA Roadmap plans to be embedded in JIRA dashboard similar to how it works in Confluence
  38. Suggestion
    JSWCLOUD-17512Allow reordering Active Sprint
  39. Suggestion
    JSWCLOUD-18566Create issues under epics on different projects on New Issue View
  40. Suggestion
    JSWCLOUD-24213Create Version Component error - Please ensure that project matches your rule's scope as specified in the 'Rule details' section
  41. Suggestion
    JSWCLOUD-27005Improve the trigger "Version Updated" - Automation for Jira
  42. Suggestion
    JSWCLOUD-23314Integration between Instances
  43. Suggestion
    JSWCLOUD-16286Improve 'Manage Sprint' permissions when the filter is complex re JSM projects
  44. Suggestion
    JSWCLOUD-16420Allow transitions for multiple issues on status with screen
  45. Suggestion
    JSWCLOUD-18871Σ Time Spent-aggregatetimespent on Epics does not sum up child issue time spent values on Classic projects
  46. Suggestion
    JSWCLOUD-20460Native support for Integration with Azure Devops
  47. Suggestion
    JSWCLOUD-18704Create a REST API endpoint to retrieve the percentage of completed issues inside Epics
  48. Suggestion
    JSWCLOUD-27777Add the 'time tracking' field to the columns in the List view.
  49. Suggestion
    JSWCLOUD-17549Adding Fields to Email Notifications
  50. Suggestion
    JSWCLOUD-25684Allow user to configure the column in the Version Release Page
Refresh results
1 2 3 4Next >>
17 of 174
Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-10460

Sprint field showing 'None' causes confusion

Log In
Gathering Interest
Export
undefined
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
      • affects-server
      • estimate
      • jsw-s2
      • triaged
    • 46
    • 25
    • 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.

            • Sort By Name
            • Sort By Date
            • Ascending
            • Descending
            • Thumbnails
            • List
        1. SprintFieldIsNone_1.png
          SprintFieldIsNone_1.png
          102 kB
          04/Mar/2014 5:07 PM
        2. SprintFieldIsNone_2.png
          SprintFieldIsNone_2.png
          75 kB
          04/Mar/2014 5:07 PM

        is related to

        Suggestion - JSWSERVER-10460 The Sprint field is none even though it is not empty

        • Closed

        Suggestion - JRACLOUD-90822 [Tracked in Issue Links] various tickets regarding confusion around sprints functionality

        • Gathering Interest

              • All
              • Comments
              • Work Log
              • History
              • Activity

              Greg Roy added a comment - 18/Apr/2025 1:57 PM

              Since this was corrected for Jira Server, (http://jira.atlassian.com/browse/JSWSERVER-10460) I'd hope it wouldn't be too hard to apply to Jira Cloud.

              When a filter from issue search is pulled forward to the dashboard it shows the sprint, or when exported, so it can be shown.

              Greg Roy added a comment - 18/Apr/2025 1:57 PM Since this was corrected for Jira Server, ( http://jira.atlassian.com/browse/JSWSERVER-10460) I'd hope it wouldn't be too hard to apply to Jira Cloud. When a filter from issue search is pulled forward to the dashboard it shows the sprint, or when exported, so it can be shown.

              Jenny Bellas added a comment - 31/Mar/2025 2:34 PM

              Seems like this also happens when a story is completed in the sprint. When that sprint closes, it says None +1. Seems like it should keep the sprint the story was completed in.  

              Jenny Bellas added a comment - 31/Mar/2025 2:34 PM Seems like this also happens when a story is completed in the sprint. When that sprint closes, it says None +1. Seems like it should keep the sprint the story was completed in.  

              Skip Gorski added a comment - 12/Mar/2025 1:04 PM

              Agreed! This needs to be addressed.

              Skip Gorski added a comment - 12/Mar/2025 1:04 PM Agreed! This needs to be addressed.

              Ian Morris added a comment - 30/Dec/2024 9:05 PM

              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 - 30/Dec/2024 9:05 PM Also seeing this issue. Definitely causing confusion, and adds difficulty to querying the information I need when planning future work.

              Refan Andros added a comment - 23/Sep/2024 9:30 AM

              a 10 years bug and still confusing the calculation

              Refan Andros added a comment - 23/Sep/2024 9:30 AM a 10 years bug and still confusing the calculation

              Ryan Coles added a comment - 19/Jun/2024 6:13 AM

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

              Ryan Coles added a comment - 19/Jun/2024 6:13 AM This is causing problems for us as well. Has anyone found a workaround? 

              James Wicks added a comment - 08/Nov/2023 8:10 AM

              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 - 08/Nov/2023 8:10 AM 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 - 02/Oct/2023 12:08 PM - 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 - 02/Oct/2023 12:08 PM - 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.

              denis.kochergin added a comment - 14/Feb/2023 6:39 PM

              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 - 14/Feb/2023 6:39 PM 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.

              Anusha Rutnam added a comment - 30/Jan/2023 10:31 PM

              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 - 30/Jan/2023 10:31 PM 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"

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

                  Created:
                  04/Mar/2014 5:07 PM
                  Updated:
                  4 days ago 2:34 AM
                  • Atlassian Jira Project Management Software
                  • About Jira
                  • Report a problem
                  • Privacy policy
                  • Notice at Collection

                  Atlassian