-
Suggestion
-
Resolution: Duplicate
-
None
-
10
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
We need to implement concurrency controls for update functions.
– Edwin
- duplicates
-
JRASERVER-6146 Implement issue locking
- Gathering Interest
- incorporates
-
JRASERVER-12253 Post submitted comment text on 'Workflow Changed' error screen
- Closed
- is blocked by
-
JRASERVER-6146 Implement issue locking
- Gathering Interest
- is duplicated by
-
JRASERVER-5154 concurrent modification of issue but 2 people causes error screen
- Closed
- is related to
-
JRASERVER-6362 Users can clobber each other's changes
- Closed
-
JRASERVER-10170 Improve concurrency handling in JIRA
- Closed
-
JRASERVER-11382 Remote API concurrency issue
- Closed
-
JRASERVER-26005 As a program, I can opt into some form of optimistic locking when updating and issue via REST
- Closed
-
JRASERVER-6146 Implement issue locking
- Gathering Interest
- relates to
-
JRASERVER-12796 Multiple values being stored for single value custom fields
- Closed
-
JRASERVER-13263 IssueNotFoundException is thrown right out to the user if a workflow action is taken on a deleted issue
- Closed
-
JRASERVER-30164 Updating the More than one value stored for custom field id ERROR to a WARNING Message
- Closed
-
JRACLOUD-1917 Control Concurrency for Update Functions in JIRA
- Closed
- mentioned in
-
Page Loading...