Thank you for a deep insight in JPD. I was wondering, from 4:08 and onwards you have a visual I can't seem to make. On your tab impact assessment you have a column "key costumers" how did you created this field?
The way to get this field is to create a new one as an administrator of a project. This particular one you're asking about is a multi-select type with weights added to each entry. The icon is just there as an option as well :)
I'm not sure if this is the right way to do it. If this project never was in JPD, then it's probably better to measure progress differently, by status, or by tools like BigPicture, or Structure, or Advanced Roadmaps. To do it in JPD, you need the ticket in a JPD. Also progress is measured based on closed Deliveries, which can be added only from a JPD type of a Jira project. Theoretically you can move tickets from one Jira project (Scrum type for example) to JPD project, but you'll most likely lose some data that you want to keep on those Epics. Therefore maybe the best solution is to create a mockup tickets for this project in JPD? It's definitely quick. Someone will have to make sure that they are in synch in terms of their status though. Possibly you can automate it, but I didn't test it yet. Interesting question :)
Actually I need to clarify one more thing: you can link Delivery tickets from outside of the JPD project, and they will update the progress when completed. I'll record a video about it today, you will see what I mean :)
Thank you for a deep insight in JPD.
I was wondering, from 4:08 and onwards you have a visual I can't seem to make. On your tab impact assessment you have a column "key costumers" how did you created this field?
The way to get this field is to create a new one as an administrator of a project. This particular one you're asking about is a multi-select type with weights added to each entry. The icon is just there as an option as well :)
@@geniusgecko-project-management Thank you!
Great tutorial - Thank you :)
From which version of Jira this is available
It's a cloud product, so doesn't matter, as cloud products are updated automatically. It's not possible to be stuck on an old version
If the delivery project has multiple Epics already, how do we get the whole project progress from JPD view then?
I'm not sure if this is the right way to do it. If this project never was in JPD, then it's probably better to measure progress differently, by status, or by tools like BigPicture, or Structure, or Advanced Roadmaps. To do it in JPD, you need the ticket in a JPD. Also progress is measured based on closed Deliveries, which can be added only from a JPD type of a Jira project. Theoretically you can move tickets from one Jira project (Scrum type for example) to JPD project, but you'll most likely lose some data that you want to keep on those Epics. Therefore maybe the best solution is to create a mockup tickets for this project in JPD? It's definitely quick. Someone will have to make sure that they are in synch in terms of their status though. Possibly you can automate it, but I didn't test it yet. Interesting question :)
Actually I need to clarify one more thing: you can link Delivery tickets from outside of the JPD project, and they will update the progress when completed. I'll record a video about it today, you will see what I mean :)
Video resolution of your screen is not so good to follow the examples
Hi! Thank you for the comment and I'm so sorry for that. I will re-edit the video and repost it with more zoom;)