Jira Automation: This component may be incompatible
Asked by Tim:

I have an automated workflow that runs off a schedule. Basically I want to create a task every quarter to review our technical documentation so it doesn't get stale.   

The work flow is super simple.

1. Trigger on the first day of the quarter
2. Create New Task in a project with required fields assigned
3. Transition the issue to the status of **Reviewed** so it shows in the first swim lane on the Kanban board and not the back log

On Step 3, it is giving a most unhelpful error message:

![CrappyErrorMessage.jpg](/t5/image/serverpage/image-id/344517iA0E6BBE13A8DE5D6/image-size/large?v=v2&px=999 "CrappyErrorMessage.jpg")

If I keep the Task in the backlog, it works fine and I can transition it manually without any field updates, but it won't let me do it via the automation.

I have looked on this board, google, GBT and see similar issues, but can't find anything to explain what "Issue" means and it's boilerplate text doesn't make sense to move it or loop it.

![JiraAutomation.jpg](/t5/image/serverpage/image-id/344524iF88BE3AEFFF4CDE6/image-size/large?v=v2&px=999 "JiraAutomation.jpg")

Anyone know where I can look (logs, searches, @Dudewithsign) that can give me more insight into the issue because the message above doesn't say much.

Thanks, Tim


Answers:
author: Simon K?nig
body: Hi,

I think your problem is that Automation might not have a "Issue" object to transition since the rule "When" is not referring to one. It might be that Automation does not register the newly created Issue to be the one it should transition.

A workaround would be to chain a Automation to the creation of this Issue.

PS: I tried the "Lookup Issue" command with a sql "created\>=-1m" but it still would not let me chose to transition the Issue.

comments: author: Tim
body: That Kinda sorta makes sense. When I just paste the whole warning message into ChatGBT it says:

### What It Means {#toc-hId--2145584203}

* **Component Dependency:** The automation rule component (such as an action or condition) that you are trying to use requires an **Issue** object to function correctly.
* **Issue Requirement:** The component you are trying to use depends on data about an issue, which should be made available earlier in the rule. This means that an issue must be identified by the automation rule before this component is triggered.

### How to Fix It {#toc-hId-341928630}

1. **Ensure Trigger Provides an Issue:** Make sure that the trigger you are using provides an issue context. Triggers like "Issue Created" or "Issue Updated" automatically provide an issue that the automation rule can use.

2. **Use a 'For Each' Branch:** If the trigger doesn't provide an issue (e.g., a scheduled trigger), you can use a "For Each" branch component to iterate over a list of issues. This will ensure that each step within the branch operates with a specific issue in context.

3. **Add an Action to Identify an Issue:** Before using the component that requires an issue, add an action earlier in the rule to search for or specify an issue. For example, you could use a "JQL" (Jira Query Language) search to find issues that match certain criteria and then perform actions on them.

Though if I'm reading this correctly it seems like a chicken/egg problem that you need to have an issue before you can schedule it's creation...


author: Simon K?nig
body: Hi, sorry I have been away.

Yes, that is what I meant.

*"This means that an issue must be identified by the automation rule before this component is triggered"*

But the Rule doesn't know the just created Issue is the one it should be using.

The only thing you could try is to chain another Rule, that looks up newly created Issues. You would have to clarify which Issues this rule should work on though.

Regards


Tags: cloud

jira-cloud