What I want to do: 10 days after create date, transition status to "At Risk" This doesn't work. I'm pretty sure it's because I need a different trigger, but I can't figure out what it would be. * Trigger: When issue is created * If Epic Name contains "TEST EPIC" * AND issue matches jql: "project=XKED AND create<= -10d * THEN transition the issue to "At Risk" I did try incorporating the epic name into the jql. Didn't help. Thanks in advance!

The OP is only a Project Admin and does not have the level of access needed to review the Post Functions for the workflow transitions.

Have you checked the 6 post functions on the transition to ensure none of them are acting on the Resolution field?

I'm a project administrator, yes. Not an Enterprise-level administrator. OK, thanks. I thought the error code would be something straightforward. I'm not going to bother them as long as the rule seems to be working.

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

transition X days after create date in Enterprise hosted version

Melody KirkWagner

What I want to do: 10 days after create date, transition status to "At Risk"

This doesn't work. I'm pretty sure it's because I need a different trigger, but I can't figure out what it would be.

Trigger: When issue is created
If Epic Name contains "TEST EPIC"
AND issue matches jql: "project=XKED AND create<= -10d
THEN transition the issue to "At Risk"

I did try incorporating the epic name into the jql. Didn't help.

Thanks in advance!

Accepted answers

All comments

Trudy P Claspill

Hello @Melody KirkWagner

You need to use a Scheduled trigger.

You can add a JQL statement to the trigger to select the issues you want.

I would advise you to add the the JQL criteria to select issues in specified starting statuses and ensure that there is actually a valid transition between those statuses and "At Risk". For instance if the issue was created more than 10 days ago but is already in a "closed" status, I assume you would not want to transition it to At Risk.

Then simply added a Transition Issue action to change the status of the found issues.

Melody KirkWagner

@Trudy P Claspill Thank you! That worked, but with an error. For others who are bumbling their way through, here are the errors I made and corrected along the way:

I selected the schedule trigger and set it for 5 minutes, then entered the jql.

Error: I didn't narrow the scope enough. I was filtering on a Condition, but that was too late in the process. The jql was searching hundreds of tickets and timed out.
- Solution: I wrote the condition into the jql
Error: I checked the "Only include issues that have changed since the last time this rule executed" box. This was a bad idea because I was only running it against one ticket to start with and I hadn't changed it. It also doesn't suit my query.
- Unchecked the box

Finally, the action was completed, but with this error:

"Transition issue

Unknown fields set during transition. Field may not be on transition screen. Fields ignored -

Resolution (resolution)"

It's true that we don't have a resolution screen and there is a resolution field - though we don't use it. I don't know how to solve for this. Let me know if I should open a new question to the community for this.

Melody KirkWagner

@Trudy P Claspill --sorry...I answered below instead of replying here.

Trudy P Claspill

Hi @Melody KirkWagner

Can you provide screen images that show all the steps in your rule and the details of the Transition Issue step?

Also provide the details from the rule Audit Log for an execution that had that error.

Melody KirkWagner

Sorry for the delay, @Trudy P Claspill I attached them and sent them last night, but they aren't here. Trying again.

1- 2023-06-07_17-08-47.jpg 5 2023-06-08_17-06-31.jpg

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

date

atl-orange