Jira Macro in Jira

Question

Is the jira Macro that exists in confluence on the product launch for Jira? I want to be able to pull Jira data into comments or the description of an issue. Here's the use case:

I'm creating a deployment ticket for development. The epic has a few issues that still need to be completed before putting into production. I want to show dev what issues still need to be completed without manually typing in each issue. If I were in Confluence I could use JQL within a Jira Macro to pull data for any issue that is in progress, or in backlog, but I don't have a way to do that in Jira.

Is this macro going to eventually be made available in Jira? Are there any workarounds to pull data into an issue in the meantime?

-Nate

Trudy P Claspill · Answer

Thanks for explaining your use case.

Unfortunately I'm not aware of any way to support it at this time.

You might want to reach out directly to Atlassian Support to find out if a suggestion like this has been made to them.

https://support.atlassian.com/contact/#/

Nate Dickinson · Answer

Trudy the use case here is to give development everything on one page. Linking issues to the deployment ticket is a manual process. In this case I have 6 issues I want to display. Any more than 2 is most likely going to be too much to do manually, or will result in a data loss, and then when the issues are resolved they will still show up in the page until they are cleared resulting in another manual process to remove.

It's great if this data populates or doesn't given filters. That's exactly what I want. If something gets fixed or is moved to complete in the epic then I don't have a need for development to see it on this screen. Having this macro would allow be to provide high level information inside a ticket without requiring dev to leave the ticket which is the desired outcome.

Data is always available somewhere else in Jira. In this case a developer could go back to the parent epic to get the incomplete issues, and then return, but that's an extra step that I don't really want them to have to take in this case. The addition of this macro to Jira would allow users to create a single document of truth for deployment requirements.

Trudy P Claspill · Answer

Hm, that is an interesting use case. I don't think I've heard of that use case before.

The results would change over time also and issues under that Epic move out of the In Progress and Backlog statuses, so there would not be a record of the requirements for deployment if you were able to embed a Jira Macro within a Description field.

Can you elaborate on why you want to put that in the Description field? Why not just link the resulting issues to the deployment issue?