Sorting fields and limit access to views

[Rebecca Graf]

Hey all,

we just started using Jira Product Discovery and there are two things we are really struggling with:

1. Depending on the view and respective audience we need to see different information. A lot of them are covered in fields but for now I do not see any chance to "group" or sort those fields in the ticket itself. They are ordered alphabetically which means that "Goal" and "KPI" have other fields in between even if they belong together.
Same for other fields like scoring values which we'd like to see as a group.
Is there any solution for that in place I didn't find yet or do I have to group them with a workaround (e.g. using a 1, 2, 3 in the beginning of a field title)

2. For us one of the biggest benefits of Jira Product Discovery is the contributor role - allowing us to share ideas with stakeholders without a full Jira License. But: We need to create different views with different sortings and level of information for various stakeholder groups. Is there any chance to create roles with limited access to certain areas (e.g. a section or a view) only? Or do they always have full access to a project?

Looking forward to your suggestions :-) 

Best regards

Rebecca

[Rohan Swami · Accepted solution]

Hi @Rebecca Graf thanks for your feedback. For 1, the best option might be to use pinned fields. When you hover on the field name in the idea view, a yellow pin will appear, and the pinned fields have their own section at the top.

For 2, the new Publish feature may address your use case: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Early-Access-Program-for-the-Stakeholders-Sharing-experience/ba-p/2572910

[Florian Lutz]

Hello everyone,
Iam also looking for the possibility to limit the access to views. Basically, I would like my contributors to see the view in which all ideas are located. In addition, I would like to offer them their own view in which they can see their own ideas and the ideas they have liked. The second view is intended to provide better traceability and an overview.
Due to the organizational structure, I would get about 100 of the personalized views with this approach, which does not seem practicable to me.

[Adam Arrowsmith]

+1 to being able to control the order and grouping of fields on the issue layout in a logical manner.