Hey there!
I would like to hide the Assign and the Assign to me button without losing their functionality. Let me explain...
We have a custom field (Owner). The Owner of a ticket is the person who is in charge of resolving an issue. The assignee of an issue (if owner != assignee) is the person who should answer a question that occured during reading / analysing the issue.
We configured a workflow for that (Request Information). The workflow works like this: The user presses the Request Information button, decides on the assignee and asks the assignee a question.
The assignee should answer this question via the workflow button (Provide Information) - not with the assign button. The Workflow then copies the Owner value to the assignee value.
Anyway, if the assignee is not the correct contact person, it should be possible to pass on an request to the correct contact person. Therefore, we use: Pass On Request (also custom workflow) where the user can choose the assignee.
I read about the workflow properties: https://answers.atlassian.com/questions/44943/can-i-remove-the-assign-and-assign-to-me-options-from-tickets-in-specific-statuses but these don't work well for my use case. They only work for the 'Provide Information' usecase, but not for the pass on request. The 'Provide Information' usecase copies the owner to the assignee field, so there is no direct assignment.
When using the properties for the 'Pass On Request' the user should be able to assign the issue to another user, but only via the 'Pass On Request' button, not the Assign / Assign to Me button. When i use the property jira.permission.assign.$group the assign button is hidden, but i can also not assign via the custom workflow button :(
Hence, I would like to know if there is any possibility to only hide those button, but not remove the functionality of the assign process.
You will have to develop some custom code Javascript/Jquery.
Jira doesn't have by default the feature that you're looking for.
Sorry :(
Add little delay in your script execution using setTimeout() .. this might solve the problem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This does the trick. However, the assign button is still visible when the status has been changed. After a refresh of the page, the button is gone.
It is a solution, but not a very sexy one :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, a delay doesn't help here, since the script (in the announcement banner) is not executed again after a workflow transition. So when opening the issue it's in a status where the buttons should be displayed, and then a workflow transition is executed and the buttons should be hidden after that transition.
FYI, currently we're testing with a modified version of this script:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok , then in this case how about using setInterval() .. I dont know if this will cause any performance issue . You can refer this post of mine
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the tip, that's a possibility. We'll need to test if there are any major drawbacks (since the script will be executed in small intervals, on every page of Jira..)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey, I'd go with a property associated with the workflow step. Haven't tried it though:
jira.permission.assign=denied
Jobin has a pretty good collection of workflow properties:
http://www.j-tricks.com/1/post/2011/02/permissions-based-on-workflow-status.html
Cheers Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, but as mentioned in my question this is not helping me :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is very helpful if you just need to hide built in actions based on status. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As workflow properties are not helping , you can hide it using javascript/Jquery,
You will need to write a script which will check for the issue status and accordingly hide the two buttons . You will need to paste this script in the announcement banner .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you give it a try by disabling the 'Assign' and 'Assign to me' button. You can disable it from here -
Hope this is inline with what you are looking for!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Almost. This hides the Assign or Assign to me button for every step in the status. I only need it hidden for one specific status (Waiting for Information) and when an issue has another status the Assign action is allowed.
Thank you, though
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I dont find that option- 'View ops bar assign link' plugin module in JIRA 6.0.2, any idea, in which module there are located?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can add a workflow property:
jira.permission.assign.denied = true
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No solution yet?
I'm dealing with the same issue.
Aviva
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andrea, you may find your solution here:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This has been mentioned in the question .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.