On 6 October 2026 a member asked on the Atlassian Community why his rule wouldn't touch the Reporter field. The rule was enabled, it used the Issue created trigger, and it was meant to set the Reporter based on who the Assignee was. "The Assignee is getting updated as expected, but the Reporter is not getting updated," he wrote. A few replies later he added the detail that explains it: "I am updating assignee manually".
If your Jira automation Issue created trigger is not working when someone assigns the work item afterwards, the rule isn't broken. Work item created, the current name of Issue created, starts the rule when the work item is created. Nobody was assigned at that moment, so the condition didn't match and the Reporter was never edited. Assigning the work item later doesn't start it again. To react to the assignment, the rule needs a trigger that listens for it: Work item assigned, or Field value changed on the Assignee field.
On 19 November 2026 we built a small version of his rule on our test site, with one condition where his has five branches, and watched it do exactly that. We created a work item unassigned, assigned it 2 minutes later, waited another 110 seconds, and the Reporter was still the person who created it. Then we built the same rule on Work item assigned, and the Reporter changed 2.7 seconds after the assignment.
Not sure this is your case? Open the rule's audit log (step 2 shows where) and look at the time of the change you expected it to react to:
- No row at that time. The trigger didn't hear the event. If a person made the change, this page is for you. If another rule made it, go to "Other reasons" at the end.
- A row that says No actions performed. The rule started and a condition didn't match. Check what the condition compares, and what that field held at that moment. Step 4 shows where to read it.
- A row with an error. The rule ran and something in it failed. Expand the row and read the message under the part that failed.
A quick note on words. Jira now says work item where it used to say issue, and since April 2026 the automation screens say flow where they used to say rule (Atlassian's release notes for 13 to 20 April). Most people still search for the old names, so the headings keep them. From here on I'll use the names on screen. That means work item and flow, plus space for what used to be a project.
What we found on 19 November 2026
- A flow on Work item created ran one time for a work item created unassigned. Its audit log shows No actions performed at 00:59:17 and nothing for the assignment at 01:01.
- The same condition and action on Work item assigned changed the Reporter 2.7 seconds after the assignment. In a team-managed space it took 2.4 seconds.
- Field value changed on Assignee changed the Reporter 2.4 seconds after an assignment, and 2.3 seconds after creation for a work item created with the assignee already set.
- When the assignee was set at creation, the Work item created flow did its job on 4 of 5 work items, in 2.4 to 2.9 seconds. The other one, the first we tried, logged Some errors and we don't know why.
- With the created flow and the assigned flow both on, one work item created with an assignee got a run from each in the same second.
We built 4 flows in the flow builder and created 10 work items, 9 of them in a company-managed space. Where I say a work item was assigned by hand, the assignment was made in the Assignee field of the work item view, signed in as a Jira admin. We scripted the browser so the clicks were the same every time, and Jira recorded each one as a change made by that user. The seconds come from the work item history, which keeps each change to the millisecond.
Before you start: role, plan and site
Note
Prerequisites — check these before step 1.
Role: space admin (project admin) or Jira admin, so you can open Space settings and then Automation. We ran every step as a Jira admin.
Product: Jira Cloud. Every screen here is from Cloud on 19 November 2026. Data Center isn't covered on this page.
Plan: Atlassian's service limits page lists automation limits for Free, Standard, Premium and Enterprise. We didn't read our own test site's plan during this run.
Permissions for the flow: the flow makes its changes as its actor, which is the account named in its settings. By default that's Automation for Jira. Atlassian's article on the "Some of the set fields aren't available" error says that account needs the Edit work items permission through the atlassian-addons-project-access role. In our space that role also held Modify Reporter.
A flow that misbehaves, or 10 minutes to build the small one below in a space where test work items won't bother anyone.
When you're done you'll have a flow that reacts to the assignment itself, and an audit log row that proves it ran.
The procedure at a glance
[[steps]]
- Reproduce it — create a work item with nobody assigned, then assign it.
- Read the audit log — find the row from creation and notice there's none for the assignment.
- Build the flow on a new trigger — use Work item assigned in place of Work item created.
- Check the Reporter action — confirm the condition, the action and the actor.
- Assign a work item and confirm — watch the Reporter change and find the Success row.
- Read the history over the API — optional, when you want the exact timestamps.
You should see the same six stages on your own site, in this order.
Why the Issue created trigger is not working after you assign the work item
A trigger is the event a flow waits for. Atlassian's trigger list describes each one briefly. For Work item created it says "The flow will run when an work item is created." (the "an" is Atlassian's). For Work item assigned it says "The flow will run when the Assignee of a work item is changed." Those are two different events, and a flow listens for the one you picked.
You won't find the word "once" on Atlassian's page. It's my reading of that first sentence plus what we measured, which was one run at creation and nothing after. Our test flow was called "Set Reporter from Assignee (on create)". It had the Work item created trigger, a condition "If assignee equals Gabriela Perdum" and an action that sets the Reporter to a second account of ours, named LeanZero SRL after our company.
Three early replies on the thread, from two members, suggested a Re-fetch work item data action or the setting that lets other automations trigger the flow. They were written before the asker said he assigns by hand, and one of them also told him to check the audit log, which is step 2 here. Both are good advice for other situations. Re-fetch refreshes the values inside a run that has already started, and Atlassian's page on flow settings describes the other setting as letting your flow "be triggered by other automation flows". A person assigning a work item is neither. My colleague Mihai answered the thread on 12 October with the trigger explanation, and the asker replied that he'd try it. We don't know yet whether it solved his case.
Step 1. Reproduce it: create the work item unassigned, then assign it
Is your own flow already misbehaving? Then use it and start at item 9. For a clean test, build the small flow first.
- In your space, select Space settings, then Automation. The page opens with the tabs Flows, Audit log, Templates and Usage.
- Select Create flow, then Create from scratch. The panel "Add a trigger" opens.
- Pick the Work item created trigger, then select Next. The panel "Add a step" opens.
- Select Condition, then Work item fields condition. The condition panel opens.
- Set Field to Assignee, Condition to "equals" and Value to a person, then select Next. The flow shows "If assignee equals" with that person's name.
- Select Action, type "Edit work item" in Search actions and select Edit work item. The action panel opens.
- In Choose fields to set, pick Reporter (System), choose the new Reporter and select Next. The flow shows "Edit work item fields" with Reporter under it.
- Select "Untitled flow" at the top, type a name and press Enter, then select Save and enable. Jira shows "Your flow has been turned on".
- Select Create at the top of Jira and type a summary. Leave the assignee alone.
- Select Create in the dialog. The new work item has nobody assigned, as long as your space's default assignee is Unassigned (ours was).
- Open the work item. In Details, select the Assignee field and pick the person your condition names. The Assignee changes straight away.
- Wait a minute or two and reload the page. The Reporter is the same as before.
You should see what we saw on SVI-1, a work item we called "Laptop request for new starter". We created it at 12:59 AM and assigned it at 1:01 AM. At 1:03 the Reporter was still Mihai, whose account had created it. And the History tab listed two entries: the creation and the assignee change.
Step 2. Read the Jira automation audit log: "No actions performed" at creation
Every run of a flow is listed in its audit log. Atlassian's debugging page says to look there first, and it gives the rule of thumb you need here: "If there are no entries and you were expecting some, you either haven't configured the trigger correctly, or the trigger has a filter on it which isn't behaving as you expect."
- In Space settings, then Automation, select the name of your flow. The flow builder opens.
- Select the Audit log icon at the top right. It's the second of the two icons just left of the Enabled toggle. A table opens with the columns Date & time, Audit log ID, Flow, Automation steps, Status and Total time.
- Find the row with the time you created the work item, and select the arrow at the start of the row. It expands into one line per part of the flow.
- Look for a row with the time you assigned the work item.
You should see a row for the creation and no row for the assignment. Ours read 00:59:17, No actions performed, 0.82s, and expanded into two lines, Work item created and Work item fields condition. So the flow started, found nobody assigned and stopped. For 01:01, when we assigned the work item, the log has nothing. If your flow has an action before its condition, as the asker's did with Add watchers, the creation row may carry another status. We didn't build that kind of flow. Whatever the creation row says, what you're looking for is the gap at the time of the assignment.
One more thing from that row: the Automation steps column shows a dash. Atlassian counts usage in steps, and its usage page says that from 5 November 2026 a run that ends as No actions performed uses none. So these quiet runs won't count once usage-based billing starts on 3 December 2026.
Step 3. Change the trigger to Work item assigned (formerly Issue assigned)
We made the change by building a second flow next to the first. I think that's also the safer way on a live site, because you can switch the original back on if the new one doesn't work.
- In Space settings, then Automation, select Create flow, then Create from scratch. The panel "Add a trigger" opens with a Search triggers box.
- In Search triggers, type "assign". One result is left under Jira, Work item assigned, described as "Flow is run when a work item is assigned to a user."
- Select Work item assigned, then Next. The panel "Add a step" opens.
- Add the same condition and the same action as in your original flow, the way items 4 to 7 of step 1 describe. The flow shows three boxes.
- Select "Untitled flow" at the top, type a name and press Enter. Ours is "Set Reporter from Assignee (on assign)".
- Select Save and enable. Jira shows "Your flow has been turned on".
- If the original flow does nothing else, open it and switch its Enabled toggle off, so the two don't both react to the same work item. If it does other work at creation, as the asker's did with Add watchers, leave it on and take the Reporter actions out of it. "Don't run both rules on the same field" below shows what we saw when both edited the Reporter.
You should see the new flow start with Work item assigned, followed by your condition and your action. Item 7 is the one item on this page we didn't click through ourselves: we switched our original flow off through the API before this test, and we never had to take an action out of a flow.
Step 4. Change the Reporter in Jira automation with Edit work item
Your condition and your action probably don't need to change. This is a check that they still say what you mean, because the trigger now runs them at a different moment.
- Select the condition in the flow. For Assignee, the Condition list offers "equals", "does not equal", "is one of", "is not one of", "is empty" and "is not empty". Ours reads "If assignee equals Gabriela Perdum".
- Select Edit work item fields in the flow. The panel "Edit work item" opens with a field labelled Reporter and the new Reporter's name in the box under it.
- Select the three-dot button at the top right (More actions), then Settings, and read the Actor field. Ours says Automation for Jira, which is the default.
You should see the actor's name, because that's the name the work item history will show. On our site the admin who did the assigning can't edit the Reporter himself: his own permission check returned false for Modify Reporter. The flow could, because it acts as Automation for Jira. We left the actor on the default. If you change it, our article on flow actors after a migration covers what to check.
The asker's branches use "is one of" as well as "equals". We ran "equals" with one person. Our run didn't manage to add a second person to the "is one of" box, so that comparison is still open.
Step 5. Assign a work item and confirm the rule ran
- Create a new work item and leave it unassigned. A new trigger doesn't replay old events, so the work item from step 1 won't update by itself.
- Open it and pick the person in the Assignee field. The Assignee changes.
- Wait a few seconds, reload the page, then select the History tab under Activity. There's a new entry from Automation for Jira.
- Go back to the flow and open its Audit log. There's a new row with the status Success.
You should see what SVI-3 showed us. We assigned it at 01:12:40 and Automation for Jira updated the Reporter at 01:12:43, 2.7 seconds later.
That Success run counted 3 steps, one for each part of our flow. For assignments that don't match the condition, Atlassian's rule from step 2 says none. A flow with an action before its condition runs that action every time, and it's counted. Our steps per rule measurements explain how to read the Usage tab; they date from October, so their numbers for failed conditions are older than the 5 November change.
Step 6. Optional: read the timestamps from the work item history
Jira's History tab rounds to the minute. For the exact gap between the assignment and the Reporter change, you can read the same history through Jira's REST API, which is Jira answering a web address with data. You need an API token (a password for scripts, made in your Atlassian account settings) and jq, a small command-line tool that picks fields out of the answer.
- In a terminal, run this with your own site address, your login and the work item key:
curl -s -u "[email protected]:YOUR_API_TOKEN" \
"https://your-site.atlassian.net/rest/api/3/issue/SVI-3?expand=changelog&fields=summary,reporter,assignee,created,status" \
| jq -r '.changelog.histories | sort_by(.created)[] | .created + " " + .author.displayName + " " + (.items[] | .field + ": " + (.fromString // "none") + " -> " + (.toString // "none"))'
We made the same request during our run and kept Jira's answer. The jq part printed this from it for SVI-3:
2026-11-19T01:12:40.990+0200 Mihai Perdum assignee: none -> Gabriela Perdum
2026-11-19T01:12:43.681+0200 Automation for Jira reporter: Mihai Perdum -> LeanZero SRL
You should see two lines for a work item the flow handled, the second one written by the flow's actor. For SVI-1, the work item from step 1, it printed a single line, the assignee change.
Field value changed for Assignee: it ran in both cases we measured
What about the Field value changed trigger? The asker wondered about it too. Atlassian uses it for assignee changes in one of its own how-to articles, and Mihai's answer on the thread said it "should work too going by the trigger docs" and that he hadn't tested it. Now we have.
In the trigger panel we set Fields to monitor for changes to Assignee, left Change type on "Any changes to the field value" and left For empty, which the panel explains as all operations.
With that trigger the Reporter changed 2.4 seconds after an assignment in the work item view (SVI-8). It also changed 2.3 seconds after creation on SVI-9, which we created through the REST API with the assignee already set. So this one flow covered both moments.
Which one should you pick? If people on your site assign after creating, Work item assigned is the plain choice and it's what the title promises. If they often pick the assignee while creating, I'd use Field value changed on Assignee, because it's the one we measured changing the Reporter at both moments. Keep in mind our creation case was a work item made through the API, so try one from the Create dialog on your site before you rely on it. Work item assigned may cover creation too: when we created SVI-4 with the assignee picked in the Create dialog, the assigned flow had an audit row for that same second. But the created flow was also on then, so we can't say the assigned flow would have changed the Reporter alone.
Don't run both rules on the same field
Mihai's October answer suggested leaving the created flow as it was and adding a second one on Work item assigned. Our run showed a side effect of that. For SVI-4, created with an assignee, both flows have a run at 01:14:16. The created flow logged Success and the history has one Reporter change. The assigned flow logged Some errors, with the message "Edited issue successfully, however some of the set fields aren't available. Fields ignored: Reporter (reporter)".
Our Reporter was correct. You'd still have an error row to explain. The flow's Notify on error setting reads "E-mail flow owner once when flow starts failing after success", and we didn't check whether a Some errors run sends that e-mail. So I'd pick one flow per field.
One "Some errors" run we can't explain
Did the two flows cause that message? We don't know, because we also saw it with one flow. Five times we created a work item with the assignee already set while the Work item created flow was on, twice in the Create dialog and three times through the REST API. Four times the Reporter changed in 2.4 to 2.9 seconds. The first time, on SVI-2, made in the Create dialog, the audit log showed Some errors with the same "Fields ignored: Reporter (reporter)" message, and the Reporter stayed as it was.
The flow, the actor and the permissions were the same all five times. Two things did differ, and we didn't isolate either: the three work items created through the API all worked, and on the other Create dialog one (SVI-4) the assigned flow was on too. Maybe the space was too new (we'd created it about 24 minutes earlier), but that's a guess. It's one run out of five, so I wouldn't build a theory on it. I do think it's a good reason to open the audit log after you change a flow.
Other reasons a Jira automation rule is not triggering
These come from Atlassian's pages and from answered Community threads. We didn't reproduce them; the option labels in the first one are from our own Settings screen.
Another flow created or changed the work item. Under More actions, then Settings, the choice reads "Only user actions can trigger this flow (default)" or "Allow other automations and user actions to trigger this flow". For a flow that should react to another flow's changes, it's the second one. The most-read of the seven Community threads we found on this trigger, with 6,008 views on 19 November 2026, is this case.
The flow started before the work item's data was ready. Two accepted Community answers (one from 2021) recommend a Re-fetch work item data action right after the Work item created trigger. Atlassian's actions page says the action "Refreshes smart values with the latest field values."
The actor can't edit the field. You'll get an error row. The article linked under Before you start lists the causes.
Atlassian had an incident. On 18 March 2026, flows triggered by Jira events were delayed between 10:06 and 13:47 UTC (status page). A glance at the status page costs less than rebuilding a flow.
If what you need is a check that stops a transition before it happens, a flow is the wrong tool for it, and our comparison of automation and workflow rules explains where each belongs.
Where our own app fits, and where it doesn't
You don't need an app for anything on this page. A different trigger is the whole answer, and it's built into Jira.
We make a Jira app called CogniRunner, and one of its parts is listeners: rules inside the app that react to Jira events directly. Its page on our site counts 68 Jira events they can react to, and it's listed on the Atlassian Marketplace. I'm mentioning it because a listener is another place to put logic that reacts to an event. There's no listener run behind this article, so I won't claim it does this job better.
What you have now
[[takeaways]]
- A way to tell a trigger problem from a permission problem: a missing audit log row against a row with an error.
- A flow on Work item assigned, or on Field value changed for Assignee, that changes the Reporter seconds after someone assigns the work item.
- One flow per field, so two flows don't both react to the same work item.
- It doesn't cover assignments made by another flow, the "is one of" comparison or a named person as actor.
If you try the Field value changed route with several people in an "is one of" condition, I'd love to hear whether it behaves on your site. It's the one piece of the original question that's still open for me :)
Originally published on leanzero.net. More Atlassian, Forge and local-AI write-ups at leanzero.net/blog, and if you're planning a migration or a Forge app, that's what we do: leanzero.net/services.










Top comments (0)