Problem

The names of the decision buttons (Approve, Consent, Reject, Abstain) and of the decisions (Approved, Rejected, Abstained) are fixed. Organizations cannot adapt them to their process, e.g. "Request changes" instead of "Reject".

Change

• In global Settings, the admin sets two names for each of Approve, Consent, Reject and Abstain: the button name (e.g. "Request changes") and the decision name (e.g. "Changes requested").

• Button names apply wherever an approver decides:

  • the approval panel in Jira and Confluence, the JSM portal;

  • quick actions and bulk actions;

  • email action buttons and the page they open;

  • Slack.

• Decision names apply wherever a decision is shown: step and approval statuses, Activity, status comments, email and Slack notifications.

• Button colors and action behavior stay as today.

Out of scope

• The "Approval Status" custom field, JQL, REST API, webhooks and CSV export keep their current values.

Acceptance criteria

• With "Request changes" / "Changes requested" set for Reject, the approver sees a "Request changes" button in the panel, the JSM portal, the approvals list, the email and Slack. After the decision, the step, Activity, status comment and notifications show "Changes requested".

• Custom Consent names apply on consent steps independently of the Approve names.

• The same decision has the same name everywhere (e.g. Activity does not show "Accepted" next to "Approved").

• Without custom names, everything looks as today. An empty field restores the default name, and a name that is too long is rejected.

• Status comments added before a rename keep the old names.

• The "Approval Status" custom field, JQL, REST API and webhooks return the same values as before the change.