Guidance on how to architect my project

Randal Boiteau March 1, 2024

Hi all!  

I am fairly certain that Jira is the solution for me, but I am moving back on forth on how to it up for this project.


I have a 'master' list of Companies that will get added one by one.
Consoto, Fabrika, etc.


For each Company, I want to track 3 different mini projects.  Each has their own workflow (So i cant use the same subtask for all of them, that would have been to easy). These three projects are the same for all companies.

ProjectA :  workflow  A>B>C>Done

ProjectB:  workflow  D>E>F>Done
etc.


Here's what I think I want to do:

  1. Issue In Project Management
  2. (automate) Create 3 subtasks 
  3. (automte) Each subtask creates an issue in a separate Kanban board, linking back to the SUBTASK
  4. Kanban board workflows, can signal the SUBTASK progress/completion



this would let be better report on the Miniproject(SUBTASK) status overall.


am I on the right track?

2 answers

0 votes
Randi Thurman March 1, 2024

It depends.

My thoughts,

Are you using the cloud or data server? Cloud has a lot more capabilities than data server.

If your companies are essentially the same (all can have the same set of fields and customized tags) then you are probably best to use one project.  If they are considerably different (i.e. one is banking, one is advertising, etc.) you may want to consider having multiple projects.  

It's best to keep your workflow as simple as possible.  Jira comes with New, In Progress, Done.  It can and probably should stay that simple.  Custom statuses and workflow are much more complicated since you have to map the whole workflow both forward and backwards when necessary.  My suggestion if you use one project is to have a custom field called Company and one called status reason, then you can have a dropdown with as many statuses as you want and not have to map the workflow.  It can still be automated that way.

 

As far as what you are automating, You don't need to have different issue types for each company if you use tabs and custom fields.

It's more complicated than this but essentially:

When "x" happens 

Then create these 3 subtasks

The next automations - there isn't enough information to give you an answer.

Why do you want to create an issue on a different board? What kind of issue do you want to create? What's your criteria for identifying progress?  Are you linking them as dependencies? 

Hope it helps.

 

 

Randal Boiteau March 1, 2024

We are Cloud.

I thought of using different boards because i could have the different columns, work flows for those.

but simplifying using a status field could just do the job.  I would just need to research how to report on that with filters I think.

 

0 votes
C_ Derek Fields
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 1, 2024

Since you have Jira Software, you can use the Epic->Issue->Subtask hierarchy to solve this. 

Since your "mini-projects" are represented by three different workflows, you would create three new Issue Types. Each Issue Type would represent the type of mini-project and would have its own workflow assigned in the Workflow scheme.

Each Company would be represented as an Epic. When you create the Epic, an automation would create three issues, one of each type, having the Epic as the parent.

Then you could easily see the status of all of your projects or filter down to just the specific Epic (Company) that you want to view, all on the single Kanban board. 

Does that help?

Randal Boiteau March 1, 2024

it does thank you. i may have been over thinking this a bit.


Im going to test this out now to see if itll meet the needs

 Thanks!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events