Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-34627

linking Confluence page to a JIRA component

XMLWordPrintable

    • We collect Confluence 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      we would like to have the ability to link a JIRA component to a confluence wiki page. This would mean that from a project's component page in JIRA our users can quickly link to an information page in Confluence that has details about that component. Please let me know if you'd like more details.

            [CONFSERVER-34627] linking Confluence page to a JIRA component

            ARTTeam added a comment -

            also for me should be very useful

            ARTTeam added a comment - also for me should be very useful
            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3564446 ] New: JAC Suggestion Workflow 3 [ 4339310 ]

            Brendon Allen added a comment -

            +1 would like to have this feature

            Brendon Allen added a comment - +1 would like to have this feature

            chrisbanm added a comment -

            +1. We use components and mini projects with in larger projects and those each have their own set of requirements. Please reconsider this issue and implement.

            chrisbanm added a comment - +1. We use components and mini projects with in larger projects and those each have their own set of requirements. Please reconsider this issue and implement.

            John McCann added a comment -

            +1

            John McCann added a comment - +1

            Anne EQS added a comment - - edited

            +1

            If I'm not mistaken this one is related: https://jira.atlassian.com/browse/JRASERVER-64169

            ..and they're gathering interest there.

            ..and this one would at least provide a workaround if solved: https://jira.atlassian.com/browse/JRASERVER-39696

             

            Anne EQS added a comment - - edited +1 If I'm not mistaken this one is related: https://jira.atlassian.com/browse/JRASERVER-64169 ..and they're gathering interest there. ..and this one would at least provide a workaround if solved: https://jira.atlassian.com/browse/JRASERVER-39696  
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3186144 ] New: JAC Suggestion Workflow 4 [ 3564446 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]

            Wayne Fisher added a comment -

            +1

            We use components (and the subcomponent plugin) to manage 900+ objects, with each object having a specification (currently word doc)

            We want to bring those specs into Confluence but need to be able to link them to their corresponding component

             

            Wayne Fisher added a comment - +1 We use components (and the subcomponent plugin) to manage 900+ objects, with each object having a specification (currently word doc) We want to bring those specs into Confluence but need to be able to link them to their corresponding component  
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3026114 ] New: JAC Suggestion Workflow 2 [ 3186144 ]

            Benjamin Michiels added a comment - - edited

            +1

            It would make documentation way easier.

            Most of the time, documentation is related to a functional block (usually a component in JIRA), not to a single issue.

            Imagine you want to document in Confluence an interface with an external software, and this interface has 100+ related issues.

            In order to access to this page from an issue, you have to create one Jira macro (in Confluence) for each issue (since JQL does not create a link in JIRA), which is just not possible.

            Benjamin Michiels added a comment - - edited +1 It would make documentation way easier. Most of the time, documentation is related to a functional block (usually a component in JIRA), not to a single issue. Imagine you want to document in Confluence an interface with an external software, and this interface has 100+ related issues. In order to access to this page from an issue, you have to create one Jira macro (in Confluence) for each issue (since JQL does not create a link in JIRA), which is just not possible.

              Unassigned Unassigned
              bbc714ef7a9b laura.taitz@envizi.com
              Votes:
              1 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: