How to Restrict a Legacy Status to Old Issues Only?

Elgun Atahan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 3, 2025

Hi everyone,

I have a legacy status in Jira that I want to keep visible only for old (legacy) issues but not for newly created ones. My goal is:

  • The status should remain available for existing legacy issues.
  • New issues should not be able to transition into this status.
  • Ideally, the status should not be visible in workflows for new issues.

What would be the best way to achieve this? Would a workflow condition, an issue security scheme, or an automation rule be the best approach?

Thanks in advance for your suggestions!

1 answer

0 votes
Mathew Lederman
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 3, 2025

@Elgun Atahan a workflow condition is your best bet for this issue. Automation will only trigger after an issue has already been transitioned and I don't believe issue security would resolve this issue.

An easy condition is something like only users in the Administrator role can transition to the status. This allows admins to make changes if needed, but restricts from your day-to-day users.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events