Denis Paul Rising Star

Nice approach! If you have Jira Premium you could do this visually in Jira Plans with drag/drop. I really like to use this for more complex projects with dependencies. But I assume this would require several mouse moves more do achieve the outcome you automate, Jan. 

If your "delivery tracker" is a ticket in Jira, my above mentioned link is exactly the way to go. It's a two-way sync between both tools. Try it out! You can get a lot out of this. In this scenario you shouldn't duplicate the tickets with confluence action items (checkboxes). Just embed the tickets in confluence and you…

I don't totally get your question. Maybe you can explain a little more of what exactly you are trying to achieve or draw a mockup. Is this maybe what you are looking for: https://support.atlassian.com/confluence-cloud/docs/insert-the-jira-issues-macro/ With this you can embed a filtered list of jira issues in your…

That's great news! We've just implemented a workaround: https://community.atlassian.com/forums/Jira-Product-Discovery-articles/Hybrid-stakeholder-notifications-in-Jira-Product-Discovery/ba-p/3218948 😂 We're currently experiencing an issue that started around the same time as this rollout (May 18–27) and I'm wondering if it…

Update As of https://community.atlassian.com/forums/Jira-Product-Discovery-articles/Incoming-changes-Notifications-for-Contributors/ba-p/3236520 this is becoming obsolete!

It's a different product that handles SSO and you have to pay per user that uses SSO - independent of the product licenses for Jira and Product Discovery. You start to need enterprise features, so you start to pay enterprise prices. That's the freemium business model ;-)

You need Atlassian guard to do this: https://www.atlassian.com/software/guard It's 4.20$/month/user: https://www.atlassian.com/software/guard/pricing 

Hello Amit, Quick note up front: Jira does not support “sub-projects” as nested projects. The common practice is to model sub-structures through the issue hierarchy and planning layers. There are two proven approaches: 1. Multiple Jira projects + Jira Plans (formerly Advanced Roadmaps) * Idea: Each team works in its own…

Jira Premium ($14.54/user/month) includes Plans, which allows for complex, nested issue hierarchies that go beyond the standard Epic > Story > Sub-task structure. This allows you to create higher-level, custom parent-child relationships, such as Initiatives > Epics > Stories…

Based on the given info I would implement it like this: * Use workflow states to reflect the stages of discussion (New, Ready for discussion, Discussed, Rejected, Approved, ...) * Use labels for the different stakeholders. You can have codenames (Team A, B, C, ...) so noone will know who you work for. This way you can…

@Christine_Kris_ Kihanya Untested idea: Use automation: * When a ticket gets a relation of type "blocking":* see if an idea is attached to it * set a value in the idea ticket (e.g. a label) * Then you can show this in your timeline view * When the blocker is removed or the blocking ticket is closed:* remove the label *…

Just like in Jira Software you add ticket relations as @Kamila Czubaj said. Here are screenshots to illustrate:

I'd love to use an agent like this but my experience is that AI tends to asks too many questions and tickets are never "ready enough" (to phrase it a bit exagerrated). I saw this last at RovoCon Berlin last week when we tried to build such an agent. Is the Readiness Checker Agent only pointing out neccessary things or is…

Done

@Jessica Hale where's AI in this? Do you feed the output to Rovo so new employees can ask and get the right videos - or better direct answers?

@Taylor James Frey it's a very broad question you are asking here. I think it could help to read this if you are talking about Jira Product Discovery: https://support.atlassian.com/jira-product-discovery/docs/the-product-management-handbook/ There is also other software from Atlassian for different usecases. What exactly…

Could be that it only takes more time. While migrating a second field and waiting a bit to grab lunch, all entries had been migrated.

@Ashley Wilson a good point to start is reading the Atlassian Product Discovery Handbook: https://www.atlassian.com/software/jira/product-discovery/resources/handbook/introduction#why-did-we-write-this-handbook Here's how to link both systems together using the delivery…

I'm just a JSM user like you and in no way affiliated with Atlassian, so it's not "my" customer supprt team. So I unfortunately cant't help on this level.

Hi @Kritika Mohan This is not how it works at Atlassian. You need to find a solution partner to provide you this kind of consulting or ask your specific questions here. See https://partnerdirectory.atlassian.com/de for a partner in your area. See https://www.atlassian.com/software/jira/product-discovery/pricing for…

For me the whole point of JPD is to define parameters that make up the priorisation. For example using the RICE framework (Reach, Impact, Confidence, Effort). Then you can create a weighted score to have the priorisation as a result. This is described well in the Atlassian Product Discovery Handbook. But of course you can…

It seems to be solved. The template works again on my side.

The template works again on my side.

The problem is already acknowledged by Atlassian:

Already acknowledged by Atlassian:

I'd say this feature is mostly useful for the new hierachy feature in premium plans. Idea types to support this could be: opportunity/solution/experiment see https://community.atlassian.com/forums/Jira-Product-Discovery-articles/A-giant-update-for-hierarchies-issue-types-opportunity-solution/ba-p/2893631

Hi @Talitha Evely Petrato , you can turn off auto-save for changes to the view so these are only local. Hope this helps.

If you do not need Jira/Confluence integration and just want to facilitate the event, try https://retrotool.io/ Easy to use, customizable, free, ... Me and my team ♥️ this

Hi Matthew, I'm not quite sure which part of the workflow you need to design. You are talking views oder the status workflow for JPD tickets? This is our status workflow which works quite well:

@Natalie Keane For Jira Product Discovery you can find documentation here: https://support.atlassian.com/jira-product-discovery/docs/manage-your-discovery-project-workflows/ For Jira Software Cloud: https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-workflow-scheme/ It's similar and…