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!

[Trudy 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 Claspill --sorry...I answered below instead of replying here.

[Trudy 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 Claspill   I attached them and sent them last night, but they aren't here. Trying again.

[Melody KirkWagner]

I also tried checking "Ignore conditions?

Bypass workflow conditions and permissions" but I still get the resolution error. 

[Trudy Claspill]

What type of issues are you wanting this rule to execute against? I see you have this condition that you are applying to the issue retrieved by the JQL in the trigger:

• If Epic Name contains "TEST EPIC"

Are you wanting to apply this rule to Epics, or to issues that are children of Epics?

What is the issue type for the issue against which the rule ran (issue xxxx-1188)?

Can you show us the workflow transition details for the transition between that issue's starting Status and the "At Risk" status, for that issue type? I would like to see the transition screen details where there are tabs for Conditions, Validators, and Post Functions, and see the details of each of those tabs.

[Melody KirkWagner]

This rule is running against a single issue, as it's a test, and you've seen every single condition and all it's details. There is nothing more. I take it the error isn't inherently meaningful? It's a super simplistic automation.

Is there a way to show more detail than what I've shown you? I'm just clicking on each portion of the automation and copying everything there. In the example above I clicked on "Then: Transition the issue to: AT RISK. The Transition picture above is a snag-it of the entire screen. I'll add it her by itself so it will be less visually confusing. If that's not the problem, I'm afraid I'm going to need some instruction on how to capture this info.

[Trudy Claspill]

Hello @Melody KirkWagner 

I'm not asking for more details from the rule. 

I would like to get confirmation that you intentionally designed this rule to operate against Epic issue. The Condition in the rule to look at the "Epic Name" field is valid only if the issue that triggers the rule is an Epic.

Given that, I would also like to confirm that the issue you used for testing is an Epic.

Additionally I'm asking for details about the workflow that is applied to the type of issue that you are acting on in the rule. What I'm looking for is information from the Workflow for the Transition you are trying to execute; the content of each tab seen here, for example:

[Melody KirkWagner]

[Trudy Claspill]

Hello @Melody KirkWagner 

What I need now is for you to click on the arrow pointing to "At Risk" to bring up the details of that transition. If you are not a Jira Administrator, or if you got the above image using the "View the workflow" option, then you won't be able to click the arrow to get additional information. 

A Jira Administrator can access the transition details from the Administration settings > Issues > Workflow screen, accessing the appropriate workflow, and then drilling into it to reveal the details of the transition.

[Melody KirkWagner]

I think you may be expecting a view that isn't offered in Enterprise on-prem Team Projects, @Trudy Claspill . There is no tabbed view of the rule available to me as far as I can see. The picture above is just the workflow for the project, showing that it's wide open. But what's odd is that the rule seems to be expecting a Resolution screen and we don't have one.

[Trudy Claspill]

Hello Melody,

I'm 95% sure that the view I'm requesting is available in the Jira self-hosted product, but only accessible by Jira Administrators.

Are you a Jira Administrator? Do you see a gear/cog icon in the upper right corner of the screen near the search field and your avatar? If you do not then you are not a Jira Administrator and the view I'm asking about is unavailable to you.

In that case you are going to need to work with your Jira Administrators to get the information in order for me to continue to help with the debugging effort.

I will say that I don't have administrator access to a Jira Server/DC instance where I could try to replicate your scenario, so I can only get so far in trying to help you debug this with info you can provide about your environment. I'll see if I can encourage another community leader that does have Server/DC admin access to jump in on this post.

[Melody KirkWagner]

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. 

[Paul Stallworth]

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

[Trudy Claspill]

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.

[Melody KirkWagner]

@Trudy 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.