The issues assigned to an inactive user are "Unassigned" on Advanced Roadmaps

[Mattia Giol]

The issues assigned to an inactive user are "Unassigned" on Advanced Roadmaps.

Step1: I assign an issue to a user

Step2: The user leaves the company and his user is disabled.

On Advanced Roadmaps the issue is: Unassigned (pic1) while in Jira it is visible (user Deactiveted, pic2)

Is there a solution to this problem?
The project leader must be able to see the assigned issues to "Deactivated Users" and reassign them to another one.

[Jack Brickey]

Hi @Mattia Giol , when a user's account is suspended then any issue where the user is assigned will show as "deactivated" under their name in the detailed issue view. Why it shows as "unassigned" in AR is unknown by me. I think can you my have to ask Atlassian support why there is a different behavior. FWIW, I have a process in place that includes reassigning any open issues to another user before suspending the account.

[Mattia Giol]

Hi Jack,

ok I opened a ticket to the support (I let you know)

Thank you for your answer. 

[Mattia Giol]

Official answer:

I understand that a deactivated user's issue is showing as unassigned in the plan but it is assigned in the issue view. Kindly note the Advanced roadmaps being a planning interface, issues assigned to deactivated users cannot be planned and assigned capacity. Hence the issue is shown as Unassigned to ensure the correct capacity and planning can be made.

Workaround

As a workaround, you can use the below JQL to find the list of issues that are assigned to inactive users:

 assignee in (inactiveUsers())

You can filter by a project by adding "AND project = xyz" and bulk change the assignee if required.

I have gone ahead and requested the team to implement the feature to show deactivated users in Advanced roadmaps. The progress of this implementation is being tracked here:

JSWCLOUD-23518 - Deactivated users show as unassigned in Advanced roadmaps

Kindly note that all the updates of the implementation will be posted on the request above. Hence we highly recommend you to watch it and vote on it, so that you're notified if this is implemented in a future release. For your reference, you can find our policy on how we prioritise feature and improvement requests at this page. You can also add a comment to the feature request to explain your specific use-case to the developers

[Jack Brickey]

Thanks for sharing @Mattia Giol . Seems consistent with my understanding and good to see they value the idea changing the behavior enough to open a suggestion.