-
Bug
-
Resolution: Timed out
-
Low
-
2
-
Minor
Issue Summary
If we have a Select List (single pick) custom field, say “Marke” in one of the JWM TMP projects, say Project A and this field is not added to the other JWM Project, say Project B. Now when we go to the JWM Board of Project A and then go to More>>Customize Cards and select the “Marke” field, then if we go to Project B’s Board and here at More>>Customize Cards>> select “Category” field. Then if we are going back to the Board of Project A, we observe that the “Category” field got selected in Project A as well but the custom field “Marke” got de-selected.
Steps to Reproduce
- Create/Have two JWM Team Managed Projects, say Project A & Project B.
- In Project A, include a Select List field, say "FieldA" from Project Settings>>Issue Types.
- In Project B, don't include this field.
- In both projects include the field "Category".
- Now go to the JWM Board of Project A and then go to More>>Customize Cards and select the “FieldA” field, then go to Project B’s Board and here at More>>Customize Cards>> select the “Category” field.
Expected Results
The fields "Category" as well as field "FieldA" should be visible on the Cards of the Board of Project A.
Actual Results
Then if we are going back to the Board of Project A, we observe that the “Category” field got selected in Project A as well but the custom field “FieldA” got de-selected.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
VSP-35 Failed to load
[JWMCLOUD-528] Selecting a Customize cards field in one TMP JWM project, deselects other select list type fields from the Card layout of Boards of other JWM TMP projects
I've updated the title of this ticket because the initial unselected field does not have to be Category. The same thing happens for other Select List system and custom fields.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team