legacy automation default user 'Autmation for Jira' no longer appears

[James Dietrich]

We still have access to Legacy Automation in our Jira instance, but can not change the default user to 'Automation for Jira' as that user does not appear anymore.  We have several spaces where that user is the default user (its even illustrated in this support article: https://support.atlassian.com/jira/kb/update-run-as-user-for-jsm-cloud-legacy-automation/) but I just made 2 new spaces, added legacy automations, and the user is not available.  I can't add them to the project, they dont appear in my directory - they were a special 'system user' that still is working in dozens of projects, but I can't select anymore...

How can I add the default automation user to be the same as in the other 20 projects in my cloud Jira SM?

[Marc -Devoteam-]

Hi @James Dietrich 

Welcome ot the community.

Legacy automation has never been bound to "atlassian-addons-project-access" as this was not related to an app

The automation for Jira "build-in" user is only for Automation.

Legacy automation always ran as the user set as default in the main Legacy automation settings.

The KB you are referring to seems to be outdated, this seems to be based on how apps are handled now in administration instead of in Jira itself or that automation is not seen as an app anymore. 

[Joseph Chung Yin]

@James Dietrich -

Beside what @Arkadiusz Wroblewski stated, can you confirm if the "Automation for Jira" user setup is listed in your new JSM spaces?

In your space permissions configuration for Assignable users - you should have a call out to "atlassian-addons-project-access".

You can also contact Atlassian Support (https://support.atlassian.com) to obtain further assistance.

Best, Joseph

[James Dietrich]

Thank you, Atlassian-addons-project-access is throughout my permission scheme...

The "Automation for Jira" user (with the dark blue bubble avatar) is nowhere to be found... can't add it as a user to the permissions scheme, or as a user to the project... I am able to 'give up' and create a new 'no-reply' user, but again, why has this changed for the spaces I made last week vs the ones I made a few months ago....its disturbing...lol.

[Joseph Chung Yin]

@James Dietrich -

As I don't see this issue on my end, so you should contact Atlassian Support for assistance further.

Sorry.

Best, Joseph

[Arkadiusz Wroblewski]

Hello @James Dietrich 

you do not need to rely on the old Automation for Jira user here.

The practical workaround is to create a dedicated service/technical user and use that as the default user for legacy automation instead. The important part is that this user must have the right permissions, not just exist in the picker. Atlassian’s KB says the selected default user needs Service Project Agent permission for the project, and also Browse users and groups global permission, otherwise you can hit the “no options” / default-user error. 

Alternative Jira cloud have native service user Function.

So I would do it this way:

create a dedicated service user ( Atlasian Administration )

give it the required Permission Scopes 

add it to the relevant projects / roles / groups

make sure it has the permissions needed in every project where those legacy rules run.

So far I remember is pure technical user and not count against License count.

[James Dietrich]

Thank you, yes I get that is an option, but I am now nervous that half of my projects are using this "Automation for Jira" user, and half are using a user in the directory - my real quesiton becomes - what changed?  are the automations in my other 20 projects still running since "automation for Jira' isn't a user in my project?  

I thank you for the solution, but im still worried as to WHY the different spaces are behaving differently....

[Arkadiusz Wroblewski]

Well @James Dietrich 

Today I see interesting Hickups on Atlasian side so being in your shoes I will wait out a little.

I using myself Automation for Jira and doesn't noticed weird behavior.

What should be clear, Atlasian wanna slowly retire Data Center, so old Solutions sooner or later will go to Trashbin, like Old Editor in Confluence.

[James Dietrich]

Yes, I know, i'm on Jira SM cloud at this point.  I just want to ride out legacy automatons as long as possible, until they either pry them from my cold, dead hands... or they make RECEIVING a reply email from a customer a core function that doesn't consume a limited resource... you know like sending an email to a customer in the first place :).  I really appreciate the help though.  I hope its a 'hiccup' issue as you say.