Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to append to the task description some customs field values from linked issues. Edited

I would like that when an issue is transition to "In progress".

The values of several custom fields from different tickets that are blocking the actual task will be added at the bottom (or some position) from the task description.

When I try to edit the field description via automation, the only options are:

  • Field to be cleared
  • Copy from trigger issue

Is there an option to add a table with the values of custom fields; the values are inside the linked tasks which type is "blocked by"?


1 answer

@Israel Luna-Vazquez Add the following into the Description text field in the Edit Issues action

||column heading A||column heading B||
|row 1, column A data|row 1, column B data|
|row 2, column A data|row 2, column B data|
|row 3, column A data|row 3, column B data|

And then just edit the values to reflect the changed you wish to make. This will create a 2x4 table, however you can extend this by adding in more sections using the same format of the mark-up.

Hope this helps!

Hello @Callum Carlile _Automation Consultants_ the only effect when adding the text you listed is:

- The actual description was overwritten by the "empty" table generated (sorry maybe I misunderstood your suggestion)

What I want:, 

  • add at the bottom of the actual description, a table.
  • inside the table should be the information from custom fields from linked issues to the trigger task.

@Israel Luna-Vazquez Only just saw the second part of your question! 

You could use the Lookup Issues action to find the list of tasks which are 'blocked by' your current issue - your lookup would be issue in linkedIssues({{issue.key}},"is blocked by").

The issue here is that you can only retrieve a handful of field values in the lookup, so you wouldn't be able to retrieve custom field values - to do this, you may need to get an add-on such as Scriptrunner and create a script which would achieve what you are looking for.

Like Israel Luna-Vazquez likes this

And to add a table to the bottom of your description, you can add {{issue.description}} above the text  in my first answer, which will display the existing description above. However, use this carefully as if you transition to In Progress several times in a workflow, it will add the table each time to whatever is in the description field - so you may end up with multiple tables.

@Callum Carlile _Automation Consultants_  thank you.

Yes I found that only few fields are available to retrieve when using {{lookupIssues}}

I hope JIRA has enquiry to include Customs Fields in {{lookupIssues}}

What I am think to do is the following:

On each linked issue "Blocked by" from the trigger task; which has the information in Custom Fields, I will generate an automated comment that summarizes in a table the information containing these "customs fields".

Then using the smart value {{issue.comments}}

Copy the body from this last comment and add-it to the actual description of the trigger task that should summarize all that information before it is completed.

I'm not too sure this would work - instead of a custom field value, you are copying a comment from a linked task to the trigger issue, but comments are also not in the list of retrievable fields from the Lookup Issues action. Perhaps I have misunderstood your description above.


I hope JIRA has enquiry to include Customs Fields in {{lookupIssues}}

suggestion ticket for this use case was opened in Atlassian's Jira earlier this month. Vote for it, watch it, and hopefully it will be implemented in the future.

Suggest an answer

Log in or Sign up to answer
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

131 views 0 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you