Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,049
Community Members
 
Community Events
176
Community Groups

Remove fields from a company managed project

Steve I'm New Here Dec 06, 2022
Our JIRA tickets have many fields which are not relevant to us but are used by other project teams. Before I go ahead and remove them from our project, I'd like to understand the implications of my actions.

If I remove fields from our company-managed JIRA project, as an unrequired outcome, will it automatically replicate those changes to other projects?
And secondly, having read some of the documentation online, if the project was created with a template, would there be an adverse effect on other projects using the same template?
For the avoidance of doubt, I'm not proposing to alter any templates.

Thanks in advance for any help you can give.

1 answer

0 votes

Hi @Steve

Welcome to the Atlassian community.  After reading your request it seems you want to remove fields, as I understand, from a screen used in a project.

Please note that in Jira, projects can share configuration, for example, two different projects can be using the same Screen scheme or Permission scheme or Field configuration scheme, so if you change anything in those, the two projects would be affected.

When I am going to do something like removing a field, I check first that the screen is being used only for that project (if the requirement is only to disable it in only), if it is not, I copy the screen scheme and screens that are going to be updated so I can isolate the change only to the project and issue type needed.

Also, be aware that are other implications because a field could be used in:

  • Automation rules.
  • Workflows transitions, validations.
  • Field configuration, for example, the field you are removing is marked as required in the configuration field scheme.

Hopefully these fields you are going to remove is not in any of those and it's an easy trip.

I hope this answers your question.
David

Steve I'm New Here Dec 07, 2022

Thanks David, I've noted your suggestions and will investigate with the team's help.

Suggest an answer

Log in or Sign up to answer