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

How to block issue transition when comments or worklog empty (Next Gen)

Josh Allen_93onke

I'd like to block an issue in a Next Gen project that's in Review but work hasn't yet been logged, either in comments or work log so that team members who don't log their work are unable to move issue to done.

I've looked a bit at automation, but since Comments and Work Log aren't fields, it's a bit more challenging. I'm wondering if there's some JQL that someone has thought of to do this?

Thanks

Accepted answers

Josh Allen_93onke

Okay, I've essentially found a way. I wasn't able to block the issue transition, but I was able to add a notification via email or MS Teams/Slack if an issue has no comment or has no logged work.

Answer:

In Next Gen, use Jira Automation to create a new rule
Trigger: Issue Transitioned (I used from In Progress to In Review)
Condition: Advanced Compare Condition
- First Value: {{worklog.comment}}
- Condition equals
- Second value empty
Action: Send email

You can also do this with comments using same Condition and first value {{comment}}

I found this page to be helpful:

https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/

Screen Shot 2020-09-04 at 8.40.53 AM.png

All comments

Trudy P Claspill

Are you working with a Classic or Next-Gen project?

In a Classic project you can modify the workflow transition to add a Condition to disallow the transition unless Time Spent > 0. That addresses your requirement to have work logged.

You can also add a Validator to a workflow to prevent completion of the transition unless the user enters a comment. You would have to add a screen includes the Comment field to the transition so that they could enter a comment during the transition. And that would not be able to check if a Comment of any kind had previously been entered on the issue. It would simply require the user to enter a comment as part of the transition.

Josh Allen_93onke

Oops, that would have been helpful information. Apologies.

I'm using Next Gen.

Josh Allen_93onke

Okay, I've essentially found a way. I wasn't able to block the issue transition, but I was able to add a notification via email or MS Teams/Slack if an issue has no comment or has no logged work.

Answer:

In Next Gen, use Jira Automation to create a new rule
Trigger: Issue Transitioned (I used from In Progress to In Review)
Condition: Advanced Compare Condition
- First Value: {{worklog.comment}}
- Condition equals
- Second value empty
Action: Send email

You can also do this with comments using same Condition and first value {{comment}}

I found this page to be helpful:

https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/

Screen Shot 2020-09-04 at 8.40.53 AM.png

Stefan Anghel_wkprlg

"In a Classic project you can modify the workflow transition to add a Condition to disallow the transition unless Time Spent > 0. That addresses your requirement to have work logged."
@Trudy P Claspill How exactly can that be achieved? Workflow conditions of type "Value field" do not allow check against "Time Spent".

I've tried checking against "Log Work" != null, but it does not seem to work....

I'm trying to configure a Classic (Software development) project on Cloud..

Trudy P Claspill

@Stefan Anghel

I have no problem selecting Time Spent as a field in the Value Field Condition

Screen Shot 2021-05-04 at 7.59.29 AM.png

Screen Shot 2021-05-04 at 8.02.11 AM.png

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-software

jira-software-cloud