-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Request the ability to Hide the "Assign this Issue" function under "Operations".
This forces the users to use the "Available workflow actions" and not assign an issue outside the workflow.
This is really causing a problem for our team especially since we have many new users.
For example, a ticket is in QA and a business user who reported it and watching it will assign it to a business person to sign off. It is still in a QA status and the business person cannot do anything with it as they have no Available Workflow actions.
- duplicates
-
JRASERVER-10242 Convert all JIRA's issue operations to use the plugin system
-
- Closed
-
-
- Closed
- is duplicated by
-
- Closed
- is incorporated by
-
- Closed
[JRASERVER-11640] Ability to Hide the "Assign this Issue" function under "Operations"
It says that this issue is incorporated by JRA-8874. But I don't really see a relation. JRA-11640 is about hiding the "Assign this issue" operation. If JRA-11640 would be implemented separately then JRA-8874 might become obsolete because people can use their own screens in their workflows and don't really need to customize the Assign Issue screen anymore.
Michael Morett
added a comment - Unless I am mistaken, when you disable the operation via the Admin section, two things happen:
--the Assign issue link goes away (as you described)
--but the Assigned To field in any screens used (i.e. Edit screen) also goes away so the issue can never be assigned unless it is assigned programmatically in a Post Function.
We have the same problem Teri described. People can assign tickets to other people without going thru workflow thereby putting tickets in an inconsistent state. If we can remove the Assign issue link only, then all assignments are then made via a screen which is displayed via a workflow action.
The next question is "isn't it still possible for a ticket to get into an inconsistent state when the assignment takes place in a screen?"
I'm not sure...we never got that far to test the theory. What I planned was to have the screen that Edit used to not have the Assigned To field. Now, all assignments happen via workflow transtions and associated screens. This then leaves the only gap in the system to be the case where one purposely chooses a workflow transition and assigns it to the wrong person. If we can limit the persons that can be chosen per workflow transition, then that gap is closed, but I could never get this far due to the original problem described above.
Michael Morett
added a comment - Unless I am mistaken, when you disable the operation via the Admin section, two things happen:
--the Assign issue link goes away (as you described)
--but the Assigned To field in any screens used (i.e. Edit screen) also goes away so the issue can never be assigned unless it is assigned programmatically in a Post Function.
We have the same problem Teri described. People can assign tickets to other people without going thru workflow thereby putting tickets in an inconsistent state. If we can remove the Assign issue link only , then all assignments are then made via a screen which is displayed via a workflow action.
The next question is "isn't it still possible for a ticket to get into an inconsistent state when the assignment takes place in a screen?"
I'm not sure...we never got that far to test the theory. What I planned was to have the screen that Edit used to not have the Assigned To field. Now, all assignments happen via workflow transtions and associated screens. This then leaves the only gap in the system to be the case where one purposely chooses a workflow transition and assigns it to the wrong person. If we can limit the persons that can be chosen per workflow transition, then that gap is closed, but I could never get this far due to the original problem described above. Teri,
This is available in 3.7.
All operations have been implemented as plugins and can be disabled in the Admin section. Simply disable it and teh operation will go away.
Cheers,
Nick
if they fix JRA-8874 you could remove the Assignee field from the Assign To screen (which for most people would be kind of counter-intuitive, but for you might help).
How is this to be done in version 6.2 as ti seems all previous options and workarounds are gone?