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

Ability to see assigned JIRA issues in Confluence WorkBox tasklist

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.

      The notifications center in confluence has a lot of potential, but I really feel we are missing so many avenues for strong interaction between Conflience and Jira.

      Can I have my Confluence task list auto-populate with my assigned JIRA tickets?

            [CONFSERVER-26818] Ability to see assigned JIRA issues in Confluence WorkBox tasklist

            Adam Barnes (Inactive) added a comment -
            Atlassian update

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Atlassian update Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Confluence Product Management

            Travis Norling added a comment -

            Hi Sherif,

            Thanks for the reply.

            For us, its about unification. We are not a pure development (coding) team. About 20% of our users or developers, 20% are project managers and the rest are engineers or our customers/users. We use both Jira/Greenhopper and Confluence, but honestly, we could easily be using any wiki software as Confluence provides no truly valuable/deep ties into JIRA (or vice versa).

            My developers dont like using the wiki for documentation (they are used to the fluid, dynanmic nature of JIRA) and my engineers done like using JIRA as they dont know how/where to store content (documentation).

            So, the only users of Confluence workbox tasks will be pure confluence users, and sadly, they cant share (expose) their task list directly to anyone else or tie it into the larger project plan (which is in JIRA).

            Perhaps a user preference setting to allow each user to add JIRA tickets to their workbox, or better yet, a JIRA filter associated with the workbox?

            At the risk of diluting this particular request, I have also opened https://jira.atlassian.com/browse/CONF-26819 . Atlassian has great tools, made so much better by having a larger "team workflow" vision, sadly it just seems that Confluence is not being brought into the fold.

            Travis Norling added a comment - Hi Sherif, Thanks for the reply. For us, its about unification. We are not a pure development (coding) team. About 20% of our users or developers, 20% are project managers and the rest are engineers or our customers/users. We use both Jira/Greenhopper and Confluence, but honestly, we could easily be using any wiki software as Confluence provides no truly valuable/deep ties into JIRA (or vice versa). My developers dont like using the wiki for documentation (they are used to the fluid, dynanmic nature of JIRA) and my engineers done like using JIRA as they dont know how/where to store content (documentation). So, the only users of Confluence workbox tasks will be pure confluence users, and sadly, they cant share (expose) their task list directly to anyone else or tie it into the larger project plan (which is in JIRA). Perhaps a user preference setting to allow each user to add JIRA tickets to their workbox, or better yet, a JIRA filter associated with the workbox? At the risk of diluting this particular request, I have also opened https://jira.atlassian.com/browse/CONF-26819 . Atlassian has great tools, made so much better by having a larger "team workflow" vision, sadly it just seems that Confluence is not being brought into the fold.

            Sherif Mansour added a comment -

            Thanks for the feature request, Travis!

            Actually to be honest, early versions of WorkBox included the ability to see your assigned issues in the same list as your personal tasks. We thought this would be awesome to help you plan your day, and at stand-up use your mobile phone to reflect on what you did yesterday.

            We ran into a few issues here (documenting them for future reference):

            • JIRA default assignee problem
              When we first implemented this, some users had over 100+ issues in their tasklist, and it was painful to remove. Why? Out-of-the-box JIRA defaults make the project admin the default assignee. However, it became apparent to us that a lot of users weren't even aware they had all these unresolved issues assigned to them. This is really a problem we need to fix in JIRA, but clearly impacts this project.
            • Lack of a true "resolved" state in JIRA
              Because JIRA has custom workflows, it is possible for customers to have issues "Resolved" in a business sense, but not actually resolved in the JIRA system. Which meant there were a whole bunch of issues which could be never removed off someones personal task list. Again, this is something which I think the JIRA team is thinking about tackling.
            • Ability to quickly resolve issues
              This is something we would have to implement, so users can quickly get things off their list from Confluence. To do this, we would need to be able to read JIRA's custom workflow / resolution states etc... all form Confluence. Something which we can do, but would need to consider.

            I'm really interested to hear more from you about this - why do you want this? What can you see yourself doing with it? It is something we considered but weren't sure how valuable it would be to users - would love to hear more.

            Sherif Mansour added a comment - Thanks for the feature request, Travis! Actually to be honest, early versions of WorkBox included the ability to see your assigned issues in the same list as your personal tasks. We thought this would be awesome to help you plan your day, and at stand-up use your mobile phone to reflect on what you did yesterday. We ran into a few issues here (documenting them for future reference): JIRA default assignee problem When we first implemented this, some users had over 100+ issues in their tasklist, and it was painful to remove. Why? Out-of-the-box JIRA defaults make the project admin the default assignee. However, it became apparent to us that a lot of users weren't even aware they had all these unresolved issues assigned to them. This is really a problem we need to fix in JIRA, but clearly impacts this project. Lack of a true "resolved" state in JIRA Because JIRA has custom workflows, it is possible for customers to have issues "Resolved" in a business sense, but not actually resolved in the JIRA system. Which meant there were a whole bunch of issues which could be never removed off someones personal task list. Again, this is something which I think the JIRA team is thinking about tackling. Ability to quickly resolve issues This is something we would have to implement, so users can quickly get things off their list from Confluence. To do this, we would need to be able to read JIRA's custom workflow / resolution states etc... all form Confluence. Something which we can do, but would need to consider. I'm really interested to hear more from you about this - why do you want this? What can you see yourself doing with it? It is something we considered but weren't sure how valuable it would be to users - would love to hear more.

              Unassigned Unassigned
              dd89173f005c Travis Norling
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: