-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
8.20.0
-
8.2
-
4
-
Severity 3 - Minor
-
1
-
Summary
When adding the JIRA Portfolio "TEAM" custom field to a screen, if a value is present a issue history event is triggered on every update without making a change to the value. This is extremely evident when added to EDIT issue Screen
Steps to Reproduce
- Create project linked to a plan
- Create a "shared team" in the plan
- Add the "TEAM" field a screen (i.e. EDIT screen)
- Trigger the screen and update other fields without adding value to the TEAM field
- Note only updated fields are listed in issue history, Team field shows no update
- trigger the same screen again and add the shared team to the TEAM field
- NOTE Team field correctly listed in issue history as a modified item
- Trigger other field updates via the same screen without modifying the team value
Expected Results
Only updated fields are listed as modified in change history
Actual Results
Modified fields are shown correctly and on some updates the TEAM field is listed as changed but is not listed for others.
Notes
see screenshot below:
Adding TEAM to the EDIT Screen The following items DO show the update to the to the Team field of "TS board team" to "TS board team"
- Description
- Summary
- Assignee
- Clicking update without making any changes to other fields
- Priority
- Comment
BUT The following DO NOT show an update to the TEAM Field applying the same action:
- Link Issue
- Epic Link
Workaround
- Do not add the team field to the edit Screen, and only add it in a single transition that you would like to use to set the team field.
OR - Do not add team to a screen and modify values in portfolio Scope View OR under the People Section of the Main issue view.
- is caused by
-
JSWSERVER-25248 Portfolio Team field should be a fully supported JIRA field
- Gathering Interest
- links to
[JSWSERVER-25237] Adding Team Field to screen triggers history event for every update
This issue is ESPECIALLY noticeable when integrating Jira with other tools, receiving regular updates.
In our case what happens is that the integration kicks in trying to modify the issue, it doesn't actually do any changes (not per se because no field value has changed), but the 'Team' field is captured and triggers an update, therefore -> notifications.
As this can affect a lot of issues, regularly and practically at the same time, I propose this receives a higher priority than "Low" as it spams users, making them ignore notifications altogether.
Workaround
Do not add the team field to the edit Screen, and only add it in a single transition that you would like to use to set the team field.
ORDo not add team to a screen and modify values in portfolio Scope View OR under the People Section of the Main issue view.
Honestly it not a workaround, it's a proposal not to use this field 
I believe you must put the Team field in the "edit screen" in order to be able to edit directly in the People Section. This is the default behavior of the quick edit function.
Not adding the Team field to the Edit screen is not a valid workaround for us since we use the Team field to assign issues (stories but also bugs) to the proper development teams.
Portfolio wouldn't be an efficient triage tool.
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC