Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
None
-
None
-
None
Description
We have a custom field called "Needs Documentation?" that has possible values of
- User Docs
- User Release Notes
- User Docs & User Release Notes
- Internal Docs
- No
If a user sets the state in JIRA and moves the ticket through the ticket workflow (Submitted, In Progress, Resolved, Closed) that state is maintained. However, if the ticket is updated via Stash when a PR is open, Stash just pulls in the enumerated list for the pull down and sets it to the first option in the list – "User Documentation". This means someone can inadvertently change the value of a variable without knowing it.
Attachments
Issue Links
- duplicates
-
BSERV-7917 Persist custom field value on Issues modal during transition
- Closed
- is related to
-
BSERV-7917 Persist custom field value on Issues modal during transition
- Closed