Share content across Jira tickets

[Lauren Briskin]

Hi!

I'm creating a punch list of fields for engineers to build in a CMS. There are two tickets for each field:

• Field creation ticket
• Field configuration ticket

The field creation ticket has a list of acceptance criteria AND contains information about what should be considered when building the field.

The field configuration ticket has acceptance criteria which are the considerations listed in the creation ticket.

Sample field creation ticket:

All of the information in "For consideration when building" and "Possible adjustments/feature requests" appears on the configuration ticket.

If I change the information in one ticket (like a new requirement is added to the configuration), I want it to change in the other ticket so that the two align.

Is there a way that I can update in only one place and display the content in both places, like the excerpt/embed options in Confluence?

Thanks!

[Aron Gombas _Midori_]

I am not sure if there is a "more civilized" way to solve this, but in the past Atlassian used a trick to do it. They added a dummy custom field (I am not sure, maybe there was even a dummy CF type which did nothing) and they entered this info to the description of that field.

Then they added the field to the corresponding issues and screens, and bingo, the text was displayed in the "Create issue" and "Edit issue" interactions.

(There is a custom field type called "Text field (read only)". It could be used as the dummy field, I guess.)

[Wojciech Wardaszko]

Hi Lauren,

That is an interesting use case. I am certain this can be done with an Automation rule, but it depends on which fields on the issue actually hold the acceptance criteria for both ticket types.

Please share more about how the data is stored in your issue types and if there are any third-party apps involved, and we should be able to come up with a suitable automation rule.

Cheers!

[Lauren Briskin]

Thanks! No 3rd party apps involved.

This particular data is stored in the "description" field. Does that help?