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

Jira Product Discovery and FixVersion Releases

@Tanguy Crusson Has any thought been put into how to mesh Jira FixVersions with JPD ideas? 

The way that our company is using ideas is that they start as an opportunity we want to solve for and then ends up becoming the actual deliverable for the engineering team.

It would be great to understand along side the delivery view which FixVersions are delivering against the idea.


Our company is wanting to do this as well @Aaron Mosny I currently have an automation set up to update a field on ideas that have a delivery ticket linked to them in our engineering project. There's no good way to do this currently by copying the field value so I dump it into a short text field on the ideas. Here's the basic structure of my automation:

When Value changes for Fix Versions

For Linked Issues with Types: is implemented by, implements

Then Edit issue fields *

* You have to use advanced field editing with something to the tune of this: 

"fields": {
"Associated Versions (this is your field name to put into)": "{{#triggerissue.latest.fixVersions}}{{name}}{{/}}"

Like # people like this

I feel like this is what I was looking for and I'm getting close but I keep getting an error "(data was not an array (versions))"

Would you have any idea on a fix? Versions is a short text field as suggested

"fields": {
"Versions": "{{#triggerissue.latest.fixVersions}}{{name}}{{/}}"

Thanks for the feedback @Aaron Mosny . We're currently reviewing how the integration with Jira Software works. We're starting with fixing a bunch of issues in terms of how it scales first though - so we won't get to things like this in the short term yet. 

Like Aaron Mosny likes this

Thanks for the follow-up. Look forward to the integration work!


Log in or Sign up to comment

Atlassian Community Events