nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Field Pins

Jack Arndt

I did some testing with a teammate and it appears that ticket field pins are a global setting.

Is there any plan to make this unique to users? I can see this causing a lot of challenges for my users.

Accepted answers

All comments

Kalin U

Hi, Jack. The documentation for Jira Software explicitly states that:

Your pinned fields are completely personal. Only you can see the fields you’ve pinned, and your teammates will only see the fields they’ve pinned

My personal experience with Jira Service Management has also been the same. Is this not implemented in Jira Product Discovery yet?

Jack Arndt

It appears to not be.

I had a verify specific set of pins on my screen, and this was what my SM saw when he logged into JPD for the first time on his Idea tickets.

He changed the pins to a very specific set, and when I refreshed I had those as well.

Tanguy Crusson

hi @Jack Arndt you are correct everything is shared in Jira Product Discovery by default. We probably need to find a different name than "pin" for this feature as the outcome is different to Jira Software and Jira Service Management. This feature is about making sure that some fields can be seen anytime anyone opens an idea.

What's your use case for people wanting to pin different fields? That would be super useful information. Thanks!

Jack Arndt

Hi @Tanguy Crusson

We plan to track the end to end lifecycle of ideas for large roadmap items and other customer enhancements using JPD. We have different personas who will use the tool slightly differently to track the end to end flow; the need for different pinned fields will vary from persona to persona.

Our very active internal stakeholders (~30 users) will have paid access and have a set of views to:
1. Create Requests
2. View Requests
3. Escalate Requests by editing custom fields
4. Challenge Priority Scores by editing custom fields
5. Formally Request Items to be Unarchived by editing custom fields
6. Update the last time they reviewed their requests so its transparent to their management via a custom field

The above persona's set of fields deviates drastically from our Product Managers (~30 users) who:
1. Triage, Score, and Prioritize Items using RICE
2. Attach Discovery Docs
3. Identify and Tag Dependency Teams
4. Link Delivery Work Items
5. Set Roadmap Target Quarters
We also have Agile Coaches who work with our PM’s to help ensure all Idea tickets have the correct artifacts and fields filled out for each step of the process.

We are early in the process of starting a beta with 6 Agile Coaches who are wiring up existing roadmap items as Ideas. With many different fields and custom views, the lack of being able to locally pin fields has caused them some challenges and confusion; my concern is that the same thing will happen as we scale this out.

Tanguy Crusson

Thanks for the context, that makes sense.

Tere Pile

Same basic concept as above: We have 6 different platform owners and multiple 'contributors' (once we get to beta this more effectively - but I could see a similar set up as above, where I define x fields across platforms, each platform owner may want to 'save' for a unique element and then contributors who like the above play a role but may not want to or need to see what I or the platform owner has 'pinned'

Tere Pile

@Tanguy Crusson is there any update or movement on pinned fields for JPD aligning w/other Jira products?

Jack Arndt

@Tere Pile - I just submitted the following as a formal enhancement request through JPD's formal feedback channel. If you are still experiencing this limitation, might be worth submitting similar feedback through the product channel:

Need User-Specific Field Pins - High Priority for Enterprise Scale

We’re heavy JPD users (82 active users) with significant success implementing portfolio discovery workflows. Love the product and actively expanding our usage - planning to 4x our implementation through merger and new instances and plan to move to JPD Premium ASAP.

However, global field pins are becoming a serious pain point as we scale. We have numerous fields supporting different workflow needs, and forcing all users to share the same pinned fields creates unnecessary complexity.

We know user-specific pins work well in JSW/JSM. We need this same functionality in JPD to maintain efficiency as we grow.

Reference: link to thread from April 2023

https://community.atlassian.com/t5/Jira-Product-Discovery/Field-Pins/td-p/2338378

Simple request: Implement user-specific field pins to match functionality available in other Jira products.

Welcome!

It looks like you're new here. Sign in or register to get started.