-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
0
-
1
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Lot's of people, like us, need issue locking, even before Service Desk was created. And every time, this wasn't important enough.
Now with Service desk, this is ESSENTIAL!
Even with the Who's looking plugin, time is lost because hard working people try to solve the same issues, as fast as they can. Collision is inevitable.
So please, make this a priority.
The same goes for setting different default Viewable by, groups. Essential when you need to keep comments internal.
jan
- duplicates
-
JRASERVER-6146 Implement issue locking
- Gathering Interest
- relates to
-
JSDCLOUD-782 need for Issue locking, now more than ever
- Closed
[JSDSERVER-782] need for Issue locking, now more than ever
Resolution | Original: Won't Do [ 10000 ] | New: Low Engagement [ 10300 ] |
Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
UIS | Original: 1 | New: 0 |
Workflow | Original: JAC Suggestion Workflow [ 3011357 ] | New: JAC Suggestion Workflow 3 [ 3650219 ] |
Link | New: This issue duplicates JRASERVER-6146 [ JRASERVER-6146 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2664131 ] | New: JAC Suggestion Workflow [ 3011357 ] |
Support reference count | New: 1 | |
UIS | New: 1 |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2323527 ] | New: Confluence Workflow - Public Facing v4 [ 2664131 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JSD Suggestion Workflow [ 2052323 ] | New: JSD Suggestion Workflow - TEMP [ 2323527 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2047873 ] | New: JSD Suggestion Workflow [ 2052323 ] |