More Button

1 Hide system actions from ‘More’ button
2 Add a custom action

Jira's ‘More' button has 13 default options that represent various system issue actions. This page will walk you through the different customizations that can be accomplished with the Issue Navigation feature to make issue tracking more efficient and tailored to your team’s needs.

Hide system actions from ‘More’ button

Any of the 13 system actions (e.g. ‘Watch issue’) can be concealed from users using allow or block list. Allow list is already set with a default value ‘Any logged-in user’. Click on the three dots icon to edit an action allow / block list.

Configuration examples below will help to understand the restrictions logic in place:

Example 1 - Agile Boards: Only users that belong to the group ‘confluence-users’ will see the Agile Boards action in the ‘More’ button menu.
Example 2 - Rank to Top: Allow list field can never remain empty. However, the block list always overrides the allow list. Hence, in this example, the Rank to Top action will be visible to anyone except users in the ‘external-users’ group.
Example 3 - Rank to Bottom: Just like in the previous example block list always overrides the allow list. Therefore this action will be concealed from any logged-in user at all times.

Add a custom action

Custom actions can be added to the ‘More’ button.

To add a new action, see the last row under the listed system actions. At the moment issue navigation allows adding three types of entries:

Web Link: When selected this action will direct the user to a web page via the pre-configured URL. Select ‘New tab’ in the ‘Link behaviour column’ if you want to open the link in a new tab.
Transition: The button replicates the same behaviour as the default workflow transition buttons in issue navigation. A workflow transition name is required to be set in the ‘Target’ column.
Having an action that prompts a workflow transition, opens access to the full potential of a workflow post-function, such as field updates, running a script or triggering a webhook.
To set up the transition, go to a default workflow editor and select ‘Add Transition'. Loop the transition by directing it from ‘Any status’ to ‘Itself’. This way, when used it will not affect the main workflow and change the issue status. Next, select the transition in the workflow editor and set up a required post-function action.