Recommended workflow and products for product discovery, design and development

Question

Hello All -

Relatively new to use of Altassian products for end-to-end product and project management so please bear with me if anything below is too obvious.

Our end to end product lifecycle typically takes the following route (iterative of course):

* Ideas triage and discovery
* Prioritized ideas move to further discovery and design phase. Depending upon the type of project, this may involve technical design, data model design, UI/UX design etc.
* Post design, create appropriate epics and develop the product through sprints through release

We are facing some issues in managing this through Altassian.

We thought that we could do #1 through Jira Product Discovery and document our findings using the Problem and Solution templates for "Ideas". However, we cannot figure out how to move all the work into a "Project" in Jira where we can use it accomplish #2. JPD only allows creation of an issue (Task, Bug, Story, Epic etc.) from and idea.

And if we create a new Scrum project in Jira, there's no functionality to document problem, and solution design within the project (seems like the way to do it is by linking to Confluence pages within the project?).

I suspect that some (or maybe all) of this is due to our lack of experience with the product suite. What is the recommended workflow to do this effectively? I don't think our process is an outlier process so I am sure someone has already figured it all out.

Thanks

Valerie Knapp_dpp5c6 · Answer

Hi @Vikas Chowdhry , thanks for your feedback.

Honestly, I don't think there are necessarily right or wrong workflows for how to work in and between different products in Atlassian. The platform offers flexibility to do what you need to with your data.

I think the most typical use case would be turning ideas into individual tasks but I can also appreciate sometimes ideas can be bigger than one task so you might need to create a dedicated project.

Someone has documented their process for this here, using automation - https://community.atlassian.com/t5/Automation-articles/Let-s-automate-project-creation-using-Jira-Automation/ba-p/2075145

Please take a look and then you should be able to copy and adapt these rules to your context to give it a try.

Hope this helps you.

Cheers

Vikas Chowdhry · Answer

Hi @Valerie Knapp - thank you for your response. I should have been more clear in my original description.

To clarify - I am able to create any type of Issue from an idea - Task, Bug, Story, or Epic. So that's not an issue.

The question is - is that the right workflow in Atlassian? To create some type of issue in a project from an idea? What about the situation that I described above where after an idea has been prioritized, I want to turn it into its own project so that my team can now start the design, document meetings with end-users, track tasks etc. (essentially project management 101). What's the workflow for that in Atlassian?

Thanks.

Valerie Knapp_dpp5c6 · Answer

Hi @Vikas Chowdhry , welcome to the Atlassian Community and thanks for your question.

I did a small demo for my company about Jira Product Discovery and I didn't run into this limitation about only being able to create Epics.

For example, I created this automation

Which is creating a task and copying some data from the JPD issue.

Can you share some screens (anonymised are fine) of the problems you've had so we can give more specific advice?

Cheers