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

      Created from a Community post: https://community.atlassian.com/t5/Confluence-questions/Automatically-link-a-confluence-page-to-a-JIRA-ticket-as-the/qaq-p/1083486?

       

      At the moment when we paste a jira issue's link into a confluence page, it automatically specifies the confluence page as "mentioned on" on the JIRA issue.

      Now what I want to do is the same thing to happen but instead of having the confluence page specified as "mentioned on", I want it to directly go as "Confluence pages".

      I know it is possible to do it directly on the JIRA issue but it is something I have to directly do opposed to the action I described above.

      Basically I have a User Story issue in JIRA and I am writing the details of said US(requirements, acceptance criteria, etc) in a confluence page so I want my US specs of the confluence page directly linked to the jira issue when I paste it in confluence.

      A good representation of what I get if I only copy paste jira issues in confluence is this :

      What I want is to have the following when working in confluence(and not having to go back to the jira issue and work on it directly) :

       

            [JRACLOUD-72115] Link Confluence pages without mentioned in

            Atlassian Update - June 1, 2021

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - June 1, 2021 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

              Unassigned Unassigned
              ssifers@atlassian.com Stephen Sifers
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: