nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Customise JIRA Issue Detail Screen

Duncan DAVIES1

I was wondering whether it was possible to modify the buttons on the Issue Detail screen (Assign, Edit, Assign To Me etc) on a per project basis? Im looking in the system-issueoperations-plugin.xml, but this seems to act for all projects, not just specific ones

Thanks

Accepted answers

Renjith Pillai

Not a complete solution, but you can somewhat achieve this by doing the following.

- Remove Assign, Edit permissions for everyone in the project using the 'Permission Scheme' (this will get rid of those actions in the issue screen)

- Add required actions in your workflow for your issue types (with appropriate permissions per project role). This will bring in the new buttons as per your choice.

- Extend the value of number of buttons showns as described here if needed (http://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-Changingthenumberoftransitionbuttons)

All comments

Renjith Pillai

Not a complete solution, but you can somewhat achieve this by doing the following.

- Remove Assign, Edit permissions for everyone in the project using the 'Permission Scheme' (this will get rid of those actions in the issue screen)

- Add required actions in your workflow for your issue types (with appropriate permissions per project role). This will bring in the new buttons as per your choice.

- Extend the value of number of buttons showns as described here if needed (http://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-Changingthenumberoftransitionbuttons)

Duncan DAVIES1

Thanks Renjith - If i remove the assign/edit permission though, I assume you wouldn't be able to assign/edit in workflow transition screens (I'm about to create a test project to confirm this, but my knowledge of permissions indicates this would be the case)

Renjith Pillai

If you need the user to really select the assignee from the assignee list, yes this permission is needed. But if you are looking for post functions to do the assignment, it is not needed. Also editing permission is not needed for the custom screens that you show in the transistions which can contain the fields excepted to be updated by the user.

Dieter

The general recipe i follow to change system operations is well described here: http://forums.atlassian.com/thread.jspa?forumID=100&threadID=54321 The trick is to create a *new* web item in your own plugin with the changed behaviour. Usually you can inherit code and just override a show method or add new conditions to control the display by implementing shouldDisplay like in the example and leave the implementation of the operation untouched. Then you would just disable the original issue operation in the system pligin. Doing it that way leaves the system untouched and there is a good chance your extension still works after an upgrade.

Dieter

For a more detailled decription of web item conditions please check https://developer.atlassian.com/display/JIRADEV/Web+Item+Plugin+Module. Search for conditions on this page