New Jira/Confluence cloud use here. When I switch to that new issue view in Jira, the one with the popup modal, I lose the links to the confluence docs that i used to see in the old issue detail view (the one that comes in from the right side).
Am I missing something?
Hi everyone, I want to provide an update related to this feature.
As we have been rolling out the new issue view (it's not out to everyone just yet), we have continued to build up the functionality. There is a lot there, but we are getting close to feature parity!
One of these items is the confluence pages being shown on the new issue view. Unfortunately, there were a few other items that we needed to build before we got to this, which is why it took so long.
It is currently on our near-term roadmap and will be released soon, we are finishing a few other things then starting on it. For this, we will be providing all of the old capabilities and making it much easier to add confluence pages from a Jira issue.
We very much appreciate taking the time to share your feedback and being patient with this.
- Taylor Pechacek, PM Jira Cloud
Thanks for the update, Taylor. That's great news.
Not to diverge too much from the original topic of this question but will your next update also reenable our ability to add external-links to Jira issues? (e.g.: linking to an Atlassian Support Ticket from within our jira instances)
In the non-beta jira-issue-view, we can link to (a) jira issues, (b) confluence pages, and (c) external web pages. This functionality is important to us.
Hey @Mike Doolittle, we have a lot of surface area on the new issue view and are still working through things. After confluence pages, we will definitely be looking at external-links.
However, our first starting point would be to display external-links added via the API, not manually by the user (the old modal as you mentioned had this option).
Would you mind sharing why you need the external-links to Jira issues for atlassian support tickets, when you could just use the 'linked issues' functionality?
Or you could add it in the description / comments as a pasted URL.
If you want to email me directly or DM here, we can discuss in more detail privately. My email is email@example.com. Cheers!
I have a use case whereby I link to a spreadsheet on onedrive.
The old external link feature just fits these kinds of needs quite comfortably.
This is not yet supported in the new view but we do plan to include this feature early next year.
You will need to click through to the full view for the time being to see Confluence links.
If the new behavior doesn't meet your needs at this time, you can switch it off in your profile.
Hi Neil and Andres,
Thanks for reaching out about the new Jira issue view.
Redesigning the issue view is a big project and this feature is sadly not available yet. We don't yet have a timeframe for when we'll add it yet, but you can watch our documentation page, which we update when we add new features and functionality.
Until we make this functionality available, you can access it by clicking through to the old issue view as mentioned previously.
You can still accomplish this by clicking the issue key in the top-left of the issue to get there (in some cases, you may need to click "See the old view" when you reach the full-page view). If you use this functionality a lot, you can also opt out of the new issue view for now by going to your avatar > Personal settings and turning off the New Jira issue view switch under Labs.
You can track the bug below at this time (reported after the writing of the original post):
I'm afraid this reflects badly on Atlassian. How on earth did the developers come up with an "improved experience" that removes key functionality? Not only are the links to explicitly related Confluence pages missing AND Confluence pages in which the JIRA is mentioned, but the "share this issue" link is also missing (which has been raised as a separate problem).
Either the developers reviewed the existing fields and decided some could be ditched without consulting the customer base or the developers didn't bother to check that all the fields from the old view were included in the new view. Whichever way you look at it, it reflects badly on Atlassian.
This has significant impact on the usefulness of the two systems (Confluence and Jira) in our day to day management of work. Confluence documents our what, Jira documents our when... and now we need to take outside measures to work around an evolution of the tool set that we were not asked to participate in to ensure that our business needs were being met. It is now one full year since the issue was originally raised. What does that say?
I hope that you decide to prioritize this higher in your backlog.
I'm fine with rolling out the new view as a labs/beta feature and starting with limited functionality. But between this and the custom fields placement it would have been better to default the view to off or make a stronger "not ready for prime time" statement. I have users asking me multiple times a week where the links have gone, or even where custom fields have gone that are just way down under "Show more". No amount of internal outreach seems to be quashing the hubbub about it.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs