as the Question
Welcome to community!
Can you explain more on the use case?
Recommendations will follow but i want to understand whether you scanned through the free apps filtered through marketplace for the use cases?
e.g., https://marketplace.atlassian.com/categories/data-analytics?useCases=Reporting&price=paid
Hi @Fazila Ashraf
thanks for the greeting!
I am working with Jira and need to generate a label statistics report with the following format:
Label Hierarchy:
Required Columns:
Summary:
Here is an example of the format I am aiming for:
Labels | Labels:parent | Labels:child | T: |
---|---|---|---|
Open_App_clash | 1 | 0 | 1 |
keeps_loosing_satellites | 1 | 4 | 5 |
error_when_download_map | 1 | 9 | 10 |
Total Unique Issues | 3 | 13 | 16 |
Could you please advise how I can achieve this setup in Jira, preferably using existing gadgets or apps? I attempted to use pre-installed gadgets, but they did not provide the functionality I need. Any guidance on the proper tools or configurations would be greatly appreciated.
Thank you for your assistance!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Lin Tingyi_YMC_ , May be you can add an automation to set the label:parent and Labels:child custom fields based on the issue type and then use it in the 2 dimensional filter gadget on labels vs this field (same gadget 2 times for 2 custom field)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Fazila Ashraf ,
Thank you for the advice, I really appreciate it.
May I confirm if Jira uses other methods to manage parent-child relationships (as per the issue types you mentioned)?
Also, is it correct that the label function currently does not support a label hierarchy?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Lin Tingyi_YMC_ , In jira premium the parent child relationships issue type wise is set in the Issue type hierarchy
And the actual relationship between the issues are set per the defined issue type hierarchy through the field 'Parent'.
There is no inbuilt label hierarchy but only issue hierarchy. Labels are attributes of those issues in the hierarchy like any other field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Fazila Ashraf ,
Thanks for answering.Help me a lot,really appreciate it.
May I confirm If I want to have those issues in a hierarchy, I would need to purchase Jira Premium and create a new project that supports issue hierarchies. Is that correct?
Could you also share more information about managing issues in a hierarchy and the differences between Jira plans (e.g., Premium)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.