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; } } }

Urge reporter to verify release by automation

Silvia Saric

Hello,

I would like to force (urge...) the Reporter of each ticket to verify it once it has been released. I was thinking that an Automation would be good for that.

For example:

When a work item transitions from Ready to Release to Released, I would like an automation to inform the reporter that they need to verify it in Production. But I am not sure how though, for example, could a Comment be written and the Reporter tagged or similar?

I was specifically thinking of an Automation and not a status change, because we would like to keep "Released" in our statistics instead of telling the Reporter to mark it as "Done" for example.

Do you have any ideas or suggestions for this purpose?

Thanks in advance!

Silvia

Accepted answers

Marc -Devoteam-

Hi @Silvia Saric

You could use an automation rule for this.

Set the trigger based on a specific transition and then add an action to place a comment or sent an email to the reporter.

In the add comment action , you can mention the reporter using the smart value:

[~accountId:{{Reporter.accountId}}]

See also documentation, How-to-mention-another-user

All comments

Marc -Devoteam-

Hi @Silvia Saric

You could use an automation rule for this.

Set the trigger based on a specific transition and then add an action to place a comment or sent an email to the reporter.

In the add comment action , you can mention the reporter using the smart value:

[~accountId:{{Reporter.accountId}}]

See also documentation, How-to-mention-another-user

Bill Sheboy

Hi @Silvia Saric

Yes, and...to the suggestions from @Marc -Devoteam-

You describe sending the reminder notifications to Reporters when a work item transitions to "Released". When a person has multiple items, this could get noisy, and may lead them to ignoring the messages over time.

If you are using releases / versions with your work items, and you are also "releasing" those versions when the block of items is done, you could instead iterate over the associated reporters, sending each one a list of their work items in a single notification. To learn how to do that, please see this related knowledgebase article. The differences would be using the Version Released trigger rather than a Scheduled trigger, and checking the Reporter rather than the Assignee.

https://support.atlassian.com/automation/kb/automation-rule-to-send-single-email-for-all-issues-per-assignee-due-next/

Kind regards,
Bill

Silvia Saric

Hello @Marc -Devoteam-

Thanks a lot, this is how it turned out:

Silvia Saric

Hello @Bill Sheboy

That was an interesting suggestion too. In our case, we release approx 6-12 tickets weekly, and all of them are reported by various users. Sometimes one and the same reporter can be present for more than one ticket in that fix version, but it still will not feel spammy most likely as there are so few tickets overall.

All the best,

Silvia

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud