Details
-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
3.13, 4.0, 5.2.5
-
3.13
-
1
-
Severity 1 - Critical
-
Description
When updating an issue, JIRA does not validate the version/s and component/s are valid for the selected project. Normally this is not a problem, but it can lead to invalid components being assigned to an issue.
Steps to reproduce:
- Open an issue for editing in one browser window
- In another browser window, move the issue to a new project
- In the first browser window hit the update button
Result - the Version/s and component/s will be saved with values from the old project
Expected Result - A validation error saying the issue had been moved whilst editing
Attachments
Issue Links
- causes
-
JRASERVER-16904 Get Edit HTML of Component Systemfield no longer orders project components
- Closed
- incorporates
-
JRASERVER-16429 Remote version not validated when creating new issue over SOAP
- Closed
- is cloned from
-
JRASERVER-16498 Version/s and Component/s not validated when updating an issue
- Closed
- is related to
-
JRASERVER-14745 Bulk Move creates duplicate components
- Closed
-
JRASERVER-16517 No way to validate customfields if their values are are only valid for the current IssueContext (Project/type)
- Closed
- mentioned in
-
Page Loading...