Hi all,
On the Issue screen(the page it takes ou once you create an issue), is there a way to remove the "More Actions" button next to "Assign", "Comment"?
Our main objectve is to get the "More Actions" button to appear only once the status of the issue has changed from "open" to "In Progress"? Is this possible?
Thanks in advance
The only way to accomplish this is to edit the "issue operations plugin"
Hi Warren,
you can remove the actions globally through disabling the plugin system modules in your plugin manager.
Your main objective is not so easy to achieve and you will probably will need a custom plugin to do this. Follow the tutorials on http://developer.atlassian.com or contact an Atlassian Expert (Partner) for help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh shucks, i thought there was perhaps another method. Thanks anyways, it will just have to stay where it is! Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
I have typical requirement of hiding the "Move" issue option for certain issue type and it should be moved when it is in particular status. I followed the below link to disable the option for single project:
https://scriptrunner.adaptavist.com/5.3.1/jira/fragments/HideUIElement.html
But i only want to disable this Move option for particular issue type in certain status. Could you please help me with this. Thanks!
--Avinash Gautam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"Move issue when in certain status" - that tells me your process is broken. Move should only be used when something was created in error in the wrong place (or issue type). It's not a trivial thing to do and should not be part of a process.
However, hiding the "move" option is quite easy and you don't need script-runner to do it. Edit your workflow, and put workflow properties on every status you want to prevent move on. From memory, jira.permission.move.group = jira-administrators for example would limit it to admins only.
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.