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
    JSWSERVER-15859Ability to reopen an empty sprint.
  2. Suggestion
    JSWSERVER-26467We need a feature that validates HTML tags and generates an error if they are incorrect before setting the announcement banner
  3. Suggestion
    JSWSERVER-19959Add granular permissions relating to version control
  4. Suggestion
    JSWSERVER-24814Make hierarchy levels configurable per plan
  5. Suggestion
    JSWSERVER-24821Item Issue Hierarchy per Project
  6. Suggestion
    JSWSERVER-25490Provide a way to migrate Advanced Roadmap plans between instances
  7. Suggestion
    JSWSERVER-26170In Plans permission configuration user can only add group that they are member of
  8. Suggestion
    JSWSERVER-6135Ability to export the Sprint reports into a common format
  9. Suggestion
    JSWSERVER-7353Ability to Customize the JIRA Agile Reports
  10. Suggestion
    JSWSERVER-7992Ability to see sub-tasks in the backlog
  11. Suggestion
    JSWSERVER-20075Remove specific user from notification
  12. Suggestion
    JSWSERVER-21283Ability to configure fiscal year start month for quarterly timeline view in Advanced Roadmaps
  13. Suggestion
    JSWSERVER-24538Ability to change the date format on an Advanced Roadmap plan in Server / DC
  14. Suggestion
    JSWSERVER-25300As Admin, would like to remove locked custom fields Target Start and Target End
  15. Suggestion
    JSWSERVER-26412Allow nested JQL to be used in board configuration and show in projects
  16. Suggestion
    JSWSERVER-26453Background for Jira drop down fields doesn't show consistent behaviour - all drop down fields should be presented with same light background
  17. Suggestion
    JSWSERVER-26457Make Jira users searchable with email addresses in the user picker fields
  18. Suggestion
    JSWSERVER-5368New issues to top of backlog
  19. Suggestion
    JSWSERVER-13029Ability to see Sprint start and end dates in search results in issue navigator
  20. Suggestion
    JSWSERVER-15655Ability to add columns to Epic Issue list on Epic
  21. Suggestion
    JSWSERVER-16744Adding custom columns to Release Page
  22. Suggestion
    JSWSERVER-24771Increase the project, issue, and team limits in Plan
  23. Suggestion
    JSWSERVER-24937Automatically shift dates of dependent issues based on blocker end date change
  24. Suggestion
    JSWSERVER-25190Allow Advanced Roadmaps to Group by any custom field
  25. Suggestion
    JSWSERVER-25242Unlock the Team field
  26. Suggestion
    JSWSERVER-25247Portfolio Team Avatar
  27. Suggestion
    JSWSERVER-25259team custom field needs to be editable
  28. Suggestion
    JSWSERVER-26409Add ability to compare date fields using JQL
  29. Suggestion
    JSWSERVER-26444Opt to no update the Resolution field upon bulk edit
  30. Suggestion
    JSWSERVER-26449Linking Jira issues by "the most recently used link."
  31. Suggestion
    JSWSERVER-26466Improve basic knowledge of virtual service Agent response on JSM helpcenter portal
  32. Suggestion
    JSWSERVER-26463Epic Link picker in basic search brings Done issues by default
  33. Suggestion
    JSWSERVER-9455Ability to create a hierarchy of Epics instead of a single level
  34. Suggestion
    JSWSERVER-21080Allow Cluster Monitoring page to show the nodes load on Windows environments
  35. Suggestion
    JSWSERVER-24817Being able to add a hierarchy level between Epic and Story
  36. Suggestion
    JSWSERVER-24818Allow Hierarchy flexibility between levels
  37. Suggestion
    JSWSERVER-9707Sprint Health Gadget for completed Sprints
  38. Suggestion
    JSWSERVER-5720New "Base Swimlanes On" option for "versions"
  39. Suggestion
    JSWSERVER-11216Allow sprints to be archived
  40. Suggestion
    JSWSERVER-11952Ability to configure a default board to show for a project
  41. Suggestion
    JSWSERVER-24995Filter by parent in Portfolio
  42. Suggestion
    JSWSERVER-26461Kerberos support for outbound traffic
  43. Suggestion
    JSWSERVER-26460Show "Upgrade from" data in "Latest Upgrade Report"
  44. Suggestion
    JSWSERVER-26462Dependencies report Rollup doesn't work when "Team" is filtered in the Roadmap
  45. Suggestion
    JSWSERVER-5212As a Rapid Board User planning a project, I want the subtask estimates (both time and story points) to count towards my sprint marker estimates.
  46. Suggestion
    JSWSERVER-9167Provide ability to automatically sum estimates from sub-tasks in user stories
  47. Suggestion
    JSWSERVER-15276Simplified Workflow: add option to disable the creation of new statuses
  48. Suggestion
    JSWSERVER-20097JQL search for issues added and removed from a sprint
  49. Suggestion
    JSWSERVER-21238Support Github Cloud Enterprise organisation managed by Azure IdP
  50. Suggestion
    JSWSERVER-21245Ability to add custom columns in release page (view)
Refresh results
1 2 3 4 5Next >>
1 of 2996
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-15859

Ability to reopen an empty sprint.

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • AgileBoard
    • None
    • 1
    • 6
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      It would be nice to have the ability to reopen an empty sprint just in case issues were removed from the sprint and the sprint was complete with no issues inside of the sprint.

      If you try to reopen an empty sprint right now, you will be met with the following in the JIRA UI:

      Currently, you can bulk update a single story into the sprint --> reopen it but this can be time consuming and reopening the sprint in the database is not recommended. Being able to just use the reopen button here would be a nice enhancement.

            • Sort By Name
            • Sort By Date
            • Ascending
            • Descending
            • Thumbnails
            • List
        1. Screenshot for JIRA support.png
          Screenshot for JIRA support.png
          58 kB
          10/May/2017 7:07 PM

            • All
            • Comments
            • Work Log
            • History
            • Activity

            Andrew Dunmore added a comment - 16/May/2017 4:40 PM

            Thanks for submitting.  I'll use the workaround until this gains traction.  Thanks.

            Andrew Dunmore added a comment - 16/May/2017 4:40 PM Thanks for submitting.  I'll use the workaround until this gains traction.  Thanks.

              Unassigned Unassigned
              jsanchez2@atlassian.com Jeremy Sanchez
              Votes:
              12 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                10/May/2017 7:09 PM
                Updated:
                5 hours ago
                • Atlassian Jira Project Management Software
                • About Jira
                • Report a problem
                • Privacy policy
                • Notice at Collection

                Atlassian