Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Pro-tip: create a one-pager for every idea (using Jira Product Discovery and Confluence)

Hi everyone, 

We often get the question "how do I best link my ideas to Jira Product Discovery to documents in Confluence (specs, one-pagers, designs)?"

A little known feature of Jira Product Discovery is "hyperlink fields" - which help you do something like this:

Screenshot 2022-10-11 at 12.45.44.png

Here's how that works:


Thanks for this insight, but I do have a question to the community here or Jira themselves...


I use confluence for producing a PRD for more significant EPIC sized items with multiple user stories, I need to replicate this into separate tickets in Jira, how can I do this from the JPD without any back and forth to confluence?  That process needs to be super seamless, as each user story needs its own Jira ticket so the Dev's can create their individual tasks and change the status as necessary.

Hyperlink fields look useful!

We're experimenting there with a field for spec documents as part of a view for managing design work. Most of these we host on sharepoint. The sharepoint files render as {filename.ext}, which is not always perfect, but fairly ok (if a good name was chosen).

Should be fairly easy to see in the end which specs are still missing. Let's see whether the specs are accessible/easy to find for the development teams, from their linked delivery issues ...

Screenshot 2022-10-12 103440.png


But also thanks a lot for pointing us to description templates, @Tanguy Crusson ! Might sound strange, but so far, we basically ignored this/didn't realize what it was. Has it only recently been added? :-D We'll be sure to try this out!


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events