Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

REST API - Retrieving field configuration for an issue type (next-gen project)

Hi,

I'm wondering if it's possible to get the list of fields linked to a specific issue type when using the REST API v3 with next-gen projects.

My use case is the following (configured through JIRA interface):

- 2 issues type A and B

- 2 custom fields C and D

- field C should be displayed on issue type A only

- field D should be displayed on issue type B only

 

Is the information related to the link between A and C available somewhere in the API ?

I know this is using issue type screen schemes when in classic projects but could not find how to do it with next-gen ones

1 answer

1 accepted

2 votes
Answer accepted
Prince Nyeche Community Leader Apr 08, 2021

Hi @Romain Viallard 

I don't think the next-gen project has an exposed API simply for this, so what you might be thinking might not even be possible to do directly. However, there's always a workaround if you can combine multiple endpoints. To list all field, I believe you can do this by using the /rest/api/3/project/search endpoint parse out the field "style":"next-gen" to identify next-gen only project and grab the projectId from the payload. Then use the project id to find the issuetype on /rest/api/3/issuetype to know all the issuetype added to it and grab the issuetype id. Then lastly search the issue endpoint as you've already gotten the projects identified as next-gen, so you can know which project key it is. In that search, run through every issue filtering the issues by issuetype id and only check the issue if the issuetype are identified. At this point, you can then find the fields within a next-gen issue and probably store this information in a file and get that list that you're searching for.

Thanks for your help here Prince !

That's a bit unfortunate since I'll have to wait for issue of a specific type to be created to get the schema but that's an acceptable workaround for now.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

98 views 2 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you