Kanban analysis + quotation

[Jordan Pesout]

We are making a switch to Jira software but some things are still not clear.

In our company we worked with a classic waterfall model.

For a lot of things that we do, we need to do some (small) analysis, send a quotation to our customer, wait for approval and after approval we start programming.

How can we incorporate the analysis/quotation in a KANBAN board? I was thinking of making new issue types 'Analysis' and 'Quotation', because it is a task that needs to be done,  and adding these issues to our KANBAN board, because they also need to be done. 

Is this a good way to approach the analysis/quotation? 

And how can we remove these from the KANBAN board, because you can only remove issues that are done by releasing them?

[Petter Gonçalves · Accepted solution]

Hello Jordan,

Can you please confirm if you are using JIRA Cloud or Server?

There are several ways you can configure your Kanban project to manage your issues, it will just depend on what kind of data are relevant for your reports.

Based on the information you have provided so far, I would proceed with the following:

- I would create two issues types (just like you mentioned) and would link both issues, just to make sure it is related to the same subject

or

- I would create two issue types and link them to a parent Epic, where you would be able to manage the issue progress individually but using the Epic view to have a single view of the entire procedure.

About this question:

And how can we remove these from the KANBAN board, because you can only remove issues that are done by releasing them?

The affirmation above is only applicable for Next-gen projects of JIRA Cloud. 

On a Classic project, the issues returned by the board are based on an editable filter. That been said, you can navigate to your board > Board settings > Edit filter query and filter which issues you would like to return on the board, not necessary the not released/released ones.

For more information, you can check the documentation below:

- Creating a board

Let me know if this information helps, Jordan.

[Jordan Pesout]

Hi,

We are working on JIRA Cloud.

I was also thinkin about creating a parent Epic, with 2 issue types.  If the customers orders the analysis/quotation, we can extend this Epic with all user stories that need to be implemented.

Thanks for your answer!