Is it possible to change the recorded user that completed the sprint when it is auto-complete?

Question

Hi, 
I used the Splint auto-complete feature for the first time and the user that apears as the one closing the sprint is 'Anonymous'. 
This is very confusing and looks a bit susopicious.

Is it possible to select the user that will apears to complete the sprint? (or at least default it to the Space owner or Board Admin)?

thanks,

Ori Cohen

Viswanathan Ramachandran · Accepted Answer

hi @Ori Cohen

I'm afraid No. Similar question asked https://community.atlassian.com/forums/Jira-questions/Auto-managed-sprints-quot-Anonymous-quot-user-updated-issue/qaq-p/2668454

See also KB article - https://confluence.atlassian.com/jirasoftware/configuring-a-sprint-to-auto-start-and-auto-complete-1688898644.html

* The auto-complete job is executed by Jira’s internal scheduler rather than on behalf of a logged-in user. Atlassian chose to attribute these automated actions to Anonymous instead of impersonating an administrator or the person who configured the sprint.

Workarounds

At the moment, your options are limited. So,

* Continue using auto-managed sprints and accept that Anonymous will appear in the history.
* Disable auto-complete and have a Scrum Master or Board Admin manually complete the sprint if you require an identifiable user in the audit trail.
* Raise a feature request with Atlassian requesting that auto-managed sprint actions be attributed to.

Tomislav Tobijas · Accepted Answer

Hi @Ori Cohen ,

You could try using Jira automation for this instead of the feature you're currently using, although in automation, there's no actual action to close the sprint. You could use the webhooks, I guess, but the question there would be whether you can send the actor as well. 👀

As for the option to select an actor within the edit sprint option, this would be a nice addition, I guess. 🤔
I've tried searching for open suggestions but couldn't find one specifically for it. I'd maybe suggest reaching out to Atlassian Support and explaining the requirement to them. They can then raise a new feature request on which you can vote.

Cheers,
Tobi