-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Issue Summary
If a User is marked as external on the Admin > People, but he is part of Jira, once this user is added to a Story on Jira, he will be synced to JA as the assignee of this Story by the connector, and if the option Jira Setup > Assign Jira users to Jira Align teams when associated with stories and defects: YES he will also be added to the Team on the internal tables, but he will not be displayed on the UI.
The hint for External Users says that:
User Type defines the user as External (can only submit ideas and enhancements) or Internal (fully functioning role-based users).
Steps to Reproduce
- Set Jira Setup > Assign Jira users to Jira Align teams when associated with stories and defects: NO
- Create a user on Jira, and associate it with a Story
- Wait for the sync of the story and see if the user is created on JA
- Now change the User type to External on Admin > People: open user
- Set Jira Setup > Assign Jira users to Jira Align teams when associated with stories and defects: YES
- Now on Jira create a new story and associate with the same user
- Wait for the sync and check the Story and Team panel
- Check the internal tables for the team and see the user there
Expected Results
TBD by Product
Actual Results
The user is associated with the Story and to the Team on the backend, although the Team UI will not display him.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
JIRAALIGN-6490 When using Copy Team Member into Sprints the Members added/removed to the Sprint are not logged in Audit log
- Short Term Backlog
- resolves
-
ALIGNSP-18607 Loading...