nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Copy Story comments into respective Epic in the Epic Comments

Facundo Rua

Wondering if anyone has done a custom made script that takes the story comments and paste it on the Epic comments for any updates that are done on the Story. Wondering if any of you came across this and has solve it using a custom made script.

Clearly this cannot be done using the Automation module within Jira or I have not been able to figure this out mainly because the Comment field is not available.

Any help will be appreciated.

Accepted answers

All comments

Mark Segall

Hi @Facundo Rua and welcome to the community!

This can be done with automation:

TRIGGER: Issue Commented
CONDITION: Issue Type != Epic
BRANCH: Epic (Parent)
ACTION: Add Comment
NOTE - This will create a new comment on the epic as Jira Automation, but will not capture other important details like the originating issue and author. Here's an example of how I capture it:
- ```
*Issue:* {{issue}}
*Author:* {{comment.author.displayName}}
{quote}{{comment.body}}{quote}
```

Facundo Rua

Thanks @Mark for this. This will create a comment based on the comment added in the Story when adding it correct? I will try this out now. Appreciate the help!

Facundo Rua

Hey @Mark Segall I might be doing something wrong. Completed the steps but this is not allowing me to continue on the Add coment...

Mark Segall

You're not able to copy/paste what I had in my last comment into the comment area?

Elliot Nevis

@Mark Segall
@Mark Segall
Thanks for your comments above as it has helped!

Can you explain why when "Issue type does not equal Epic" is not included in the workflow it only allows for one comment to be added to the epic, but then when "Issue type does not Equal Epic" is included, multiple comments can be added to the Epic?

Trying to think of a reason as to why but can't wrap my head around it!

Mark Segall

Hi @Elliot Nevis and welcome to the community!

Branching can be a little awkward to wrap your head around at first. For this specific question, they wanted comments from Epic children to copy up to the Epic so issue hierarchy is important. At time of trigger, the rule does not yet know if the comment was at the Epic level or the Story/Task/Bug level.

In this use case, we don't want to take action if the issue is an Epic so we add that first condition so it exits the rule when the issue that triggered is an Epic. If this condition passes, we know its a child issue.

Now that we know it's a child issue, we need to get to our end state which is copying that comment up to its Epic. This requires a branch which tells the rule that it needs to switch its focus from whatever triggered the rule to its parent Epic.

Finally, the rule has branched into the Epic and we can perform actions directly against the Epic which in this case is copying the comment from the issue that triggered the rule.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud