• 0
    • 1
    • 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.

      Problem Definition

      According to a document Referencing issues in your development work, it says the default project key patter is ([A-Z][A-Z]+).

      However, the pattern in the recent versions of Jira applications (after 7.4.x at least) is set as ([A-Z][A-Z0-9]+).

      Suggested Solution

      The document should be updated as the recent versions of Jira are.

          Form Name

            [JSWSERVER-16652] Information about project key pattern

            Aakrity Tibrewal made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Aakrity Tibrewal made changes -
            Labels New: cleanup-seos-fy25

            Atlassian Update - 17 April 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            Please note the comments on this thread are not being monitored.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.

            Kind regards,
            Jira Data Center

            Aakrity Tibrewal added a comment - Atlassian Update - 17 April 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues , current work, and future plans. Kind regards, Jira Data Center
            Aakrity Tibrewal made changes -
            Comment [ {panel:title=Atlassian Update - 24 March 2025|borderStyle=solid|borderColor=#6554c0|titleBGColor=#6554c0|bgColor=#eae6ff|titleColor=#ffffff}

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a *lack of engagement in the last four years*, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            *Please note the comments on this thread are not being monitored.*

            You can read more about our [approach to highly voted suggestions here|https://community.atlassian.com/t5/Jira-articles/A-renewed-approach-to-highly-voted-Server-suggestions-for-Jira/ba-p/688117] and [how we prioritize what to implement here.|https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html]

            To learn more about our recent investments in Jira Data Center, please check our [public roadmap|https://www.atlassian.com/roadmap/data-center?product=jsw&] and our dashboards, which contain [recently resolved issues|https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=85597], [current work, and future plans.|https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=85890]

            Kind regards,
            Jira Data Center

            {panel} ]
            Aakrity Tibrewal made changes -
            Resolution Original: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Gathering Interest [ 11772 ]
            Aakrity Tibrewal made changes -
            Labels Original: cleanup-seos-fy25
            Aakrity Tibrewal made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            Aakrity Tibrewal made changes -
            Labels New: cleanup-seos-fy25
            Jacek Krawczyk (Inactive) made changes -
            PM Reviewed New: 16/Mar/2023
            Status Original: Gathering Interest [ 11772 ] New: In Progress [ 3 ]
            Jacek Krawczyk (Inactive) made changes -
            Assignee Original: Tomasz Bartyzel [ tbartyzel ] New: Jacek Krawczyk [ 2cd4b6cecf0f ]

              2cd4b6cecf0f Jacek Krawczyk (Inactive)
              yokamoto Yuki Okamoto (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: