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.
Jira Software Data CenterProject Type: software

Jira Software Data Center

  • Issues
  • Reports
  • Components

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-26315The Dark Theme Mode is not supported by Advanced Roadmaps For Jira
  2. Suggestion
    JSWSERVER-26031Provide support for Pgpool-II active-active configurations
  3. Suggestion
    JSWSERVER-25121Add Original Estimate to Advanced Roadmaps New Experience
  4. Suggestion
    JSWSERVER-25925MySQL default auth plugin
  5. Suggestion
    JSWSERVER-13029Ability to see Sprint start and end dates in search results in issue navigator
  6. Suggestion
    JSWSERVER-25193Release the "duplicate plan" feature for Jira Data Center
  7. Suggestion
    JSWSERVER-21581Limit the dates to fetch DVCS data
  8. Suggestion
    JSWSERVER-21773As a Gitub admin I would like to receive fewer API requests to grab user information
  9. Suggestion
    JSWSERVER-9554Customisable panels in Agile Backlog
  10. Suggestion
    JSWSERVER-11952Ability to configure a default board to show for a project
  11. Suggestion
    JSWSERVER-11992As a Jira Software user, I would like to be warned when moving issues which are in a sprint
  12. Suggestion
    JSWSERVER-15615Remove issue from Sprint before moving it to another project
  13. Suggestion
    JSWSERVER-25134Allow to show completed issues in schedule and reports pages
  14. Suggestion
    JSWSERVER-15634Duplicate sprint names creating conflicts
  15. Suggestion
    JSWSERVER-21676Introduce auth token refresh for github user tokens (ghu_) for DVCS integration
  16. Suggestion
    JSWSERVER-25232Add the ability to export Dependencies Report in Advanced Roadmaps
  17. Suggestion
    JSWSERVER-26010Improve session handling for Jira + OIDC
  18. Suggestion
    JSWSERVER-9626As a developer, I want the Issue Detail View in the plan and work mode to support the different JIRA custom field abstract classes so that my own custom field can be displayed
  19. Suggestion
    JSWSERVER-15524Make the Advanced Roadmaps "Team" field available on the Board Issue Detail View
  20. Suggestion
    JSWSERVER-20075Remove specific user from notification
  21. Suggestion
    JSWSERVER-20981HTML validator on announcement banner
  22. Suggestion
    JSWSERVER-24819Ability to add multiple values to the Parent Link field
  23. Suggestion
    JSWSERVER-25248Portfolio Team field should be a fully supported JIRA field
  24. Suggestion
    JSWSERVER-13265Provide UI method to identify origin board for a sprint.
  25. Suggestion
    JSWSERVER-15624Allow more than 3 fields on card layout
  26. Suggestion
    JSWSERVER-15878Better handle Epic Name, Epic Link, and issue exports to HTML/CSV
  27. Suggestion
    JSWSERVER-25242Unlock the Team field
  28. Suggestion
    JSWSERVER-26048Set Default 'Send mail for this update' to unticked/false for Bulk Changes
  29. Suggestion
    JSWSERVER-25378Edit Comment window (and others) way too small.
  30. Suggestion
    JSWSERVER-26396Allow changes in external directory settings even if the authenticate user is part of it
  31. Suggestion
    JSWSERVER-4452Agile board should refresh automatically whenever someone moves a card or makes another change
  32. Suggestion
    JSWSERVER-21282As a user, I want to be able to click at the Epic Name displayed on the Kanban Board card and see it at the preview
  33. Suggestion
    JSWSERVER-21353Show only roles that are used in specific project
  34. Suggestion
    JSWSERVER-20814Support of Github Apps in DVCS instead of user based OAuth
  35. Suggestion
    JSWSERVER-25025Add ability to filter by "Priority" field
  36. Suggestion
    JSWSERVER-25263Ability to reorder Team list
  37. Suggestion
    JSWSERVER-26391Horizontal Timeline View for Jira Plan Dependencies report
  38. Suggestion
    JSWSERVER-7992Ability to see sub-tasks in the backlog
  39. Suggestion
    JSWSERVER-10101As a manager with a Kanban or Scrum Board, I want to be able to dynamically group my board by an attribute so that I may more easily organize my team's work
  40. Suggestion
    JSWSERVER-19912Implement Configuration Option for CSP Header
  41. Suggestion
    JSWSERVER-21587Add 'Child issues' to 'Issue Detail View'
  42. Suggestion
    JSWSERVER-25129Advanced Roadmaps - Ability to add Jira fields such as the description field to the plan view
  43. Suggestion
    JSWSERVER-25149Date picker - start week on Monday
  44. Suggestion
    JSWSERVER-25067Custom Start and End date to be set default in plans
  45. Suggestion
    JSWSERVER-25081Improve message "This issue is missing some details that are specified in the issue sources of your plan. To make this issue visible, add these missing details to the issue." to show what is missing
  46. Suggestion
    JSWSERVER-26301Jira DC App, add support for external browser
  47. Suggestion
    JSWSERVER-2866As Project Manager, CFD colours must be consistent across all reports page and gadgets (1 status column = 1 same colour) to avoid confusion
  48. Suggestion
    JSWSERVER-7721When cloning an Epic, add the option to clone the linked Stories as well
  49. Suggestion
    JSWSERVER-9707Sprint Health Gadget for completed Sprints
  50. Suggestion
    JSWSERVER-12516As an Admin, I do not want to see closed Epics displayed in epic-link field dropdown list of a story
Refresh results
<< Previous 1 2 3 4 5Next >>
64 of 2935
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-15634

Duplicate sprint names creating conflicts

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • None
    • 6
    • 19
    • 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.

      Hi,
      I have a main agile board which displays the current and future sprints inline for the sub-boards for my Project. Now if I create a new sprint from my main board it gets displayed in my sub-boards. But when i create sprint on my sub-boards it creates the next future sprint number on my sub-board and it gets displayed on my main board with the future sprint number which is a duplicate of already created future sprint in main board. For e.g. i created a future sprint SP-18 on my main board, then i went to one of my sub-boards and created another sprint SP-18 and assigned 1 issue from backlog to it. Now it gets displayed on my main board as SP-18 with the issue attached. I now have 2 SP-18.
      Please help me resolve this conflict. It should not allow creation of same sprints which are already created.

            • Sort By Name
            • Sort By Date
            • Ascending
            • Descending
            • Thumbnails
            • List
        1. Capture1.JPG
          Capture1.JPG
          94 kB
          27/Feb/2017 6:03 AM
        2. Capture2.JPG
          Capture2.JPG
          46 kB
          27/Feb/2017 6:03 AM
        3. Capture3.JPG
          Capture3.JPG
          27 kB
          27/Feb/2017 6:03 AM

        is related to

        Suggestion - JSWSERVER-12419 Duplicate Sprint names causes multiple issues with teams

        • Closed
        mentioned in

        Page Failed to load

              • All
              • Comments
              • Work Log
              • History
              • Activity

              Tetiana Uspalenko added a comment - 01/Feb/2023 10:34 AM

              I faced the same issue in my projects. When the name of Sprint in project A was duplicated to another project B ..( and by updating sprint name A it re-writes sprint name B..
              Do you have a suggestion or workaround for this?

              Tetiana Uspalenko added a comment - 01/Feb/2023 10:34 AM I faced the same issue in my projects. When the name of Sprint in project A was duplicated to another project B ..( and by updating sprint name A it re-writes sprint name B.. Do you have a suggestion or workaround for this?

              Mark Klemm added a comment - 04/May/2018 5:35 AM

              Also see JSWSERVER-12419

              Mark Klemm added a comment - 04/May/2018 5:35 AM Also see  JSWSERVER-12419

              Mark Klemm added a comment - 04/May/2018 5:34 AM

              See https://community.atlassian.com/t5/Jira-Software-questions/How-to-stop-the-use-of-duplicate-sprint-names/qaq-p/160508

              Mark Klemm added a comment - 04/May/2018 5:34 AM See  https://community.atlassian.com/t5/Jira-Software-questions/How-to-stop-the-use-of-duplicate-sprint-names/qaq-p/160508

              Mark Klemm added a comment - 04/May/2018 5:31 AM - edited

              We have a similar issue when a Sprint name is used on another board.

              On Jira Server v7.8.1#78001-sha1:0c6698b

              Mark Klemm added a comment - 04/May/2018 5:31 AM - edited We have a similar issue when a Sprint name is used on another board. On Jira Server v7.8.1#78001-sha1:0c6698b

                Unassigned Unassigned
                e5a7ea4c8556 Meenakshi Thakur
                Votes:
                20 Vote for this issue
                Watchers:
                19 Start watching this issue

                  Created:
                  27/Feb/2017 6:04 AM
                  Updated:
                  6 days ago 4:10 AM

                    • Atlassian Jira Project Management Software
                    • About Jira
                    • Report a problem
                    • Privacy policy
                    • Notice at Collection

                    Atlassian