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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Jira Product Discovery - Naming Standard Recommendations?

I am the administrator for all Atlassian products.   I keep documentation on things like a list of our custom fields, statuses, etc. and I am wondering if anyone has run into issues with JPD fields being named the same as a Jira Software field?    I would love to know how you solved the problem of naming standards.

My thought was to prefix or suffix the field name with JPD or something similar.   Once JPD goes GA, I need to have some standards in place so I don't go nuts trying to figure out why we have what looks like duplicate field names.


2 answers

1 accepted

0 votes
Answer accepted

Hello @Gail 


I am not sure JPD (or generally, team managed projects) are compatible with a requirement to maintain a list of all custom fields separate to the project those fields make sense in.

JPD makes it really easy to create and maintain new fields per project.You can find more information on the difference between team and company projects here but it seems like team managed projects are resistant to central management and documentation like what you describe by design.



Thanks Chris.  

To clarify more - i wasn't looking to document team-managed/JPD objects.   I pulled an API call to get a list of all our custom fields.   When I reviewed it, I happened to see a duplicate named field effort.   I only knew of one field used for our company-managed projects.   In more digging I found 20 JPD fields listed.   I don't really care that they show on this list, but what I am concerned with is when they use the same name as existing objects.

These duplicate fields can be seen/used in filters, so this will be confusing to users.

I was just wondering if I needed to come up with a JPD special naming pattern before we go GA.   This was totally unexpected.    


Like David Griffin likes this

@Gail makes sense - thanks for the reply!


JPD is going to spin up those 'default' fields any time you create a new JPD project, so if you can keep pace with the maintenance then a JPD-specific prefix is the only way I can think of that will solve for field ambiguity caused by creating a JPD project. This will be the case anytime someone creates a new team-managed project in your instance, though. Hopefully that's not happening too often :D



thanks.  Luckily I am the only one allowed to create projects so I can at least keep a list of the "culprits" lol.  

Like # people like this

I’d honestly prefer they don’t show unless they’re company managed project fields, myself. 

Like # people like this
0 votes
Rohan Swami
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 22, 2023

@Gail @Chris Timms you're exactly right in the way JPD fields are created. Thanks for sharing your use case here, I was unaware customers were reviewing JPD fields through APIs!

Thanks Rohan.   That is the only way I am aware of in Cloud to get a full custom field listing without copying and pasting.   It was suggested to me by Atlassian Support.   If there is a better way, I would love to know.    

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events