You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi there! I encountered with problem that i can’t get hierarchy levels for issueTypes and somehow distinguish: epic, story, sub-task for users who still use a Jira Server. I need that because we have a users that still use a Jira Server and want to sync their issue types with custom issue type name in our App. Jira cloud rest api has that value and we can sort issueTypes by hierarchy level. Is there any solution to somehow distinguish issue types in Jira server by some uniq identifier ?
Thank you for response!
The problem is that user can change issue type name whatever he want. For example:
User can change issue type name from Story to Implementation. As result i won't know that this is Story issue type. In my implementation i need that user can pick issue type with hierarchy level 0, it means: Story, Bug, Sub-Task. Jira server rest api doesn’t include hierarchy level property for issue type, only Jira Cloud Rest Api includes.
I want to be sure that user doesn't choose epic issue type and so to be i need somehow to sort issue type by something unique.
How about giving the objects the hierarchy you want by mutating it. I know from the example server don't have it but you can always design your app to preconfigure the hierarchy by instructing the user to mention which issue type is higher than the other. i.e You can setup a configure issue type screen that will just show by means of drag and drop the level of each issueType (In the same manner Advanced roadmap does it). That way, you can have a logic you can work with within your app? Therefore, when the user changes from "Story" to "Implementation", within your code you know that story is hierarchy level 0 and Implementation is hierarchy level 1. Just my thoughts on this.