Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Setting up work flow for a manufacturing company

I'd like to start out right and setup my work flow properly. Any quick suggestions would be appreciated. We are a make to order manufacturing shop with 35 employees. Most projects require some level of customization of both hardware and software components. 

Projects include several steps of fabrication -- design, material fabrication (e.g. metal, acrylic), electrical wiring, programming, QC. Each step is approved by the project manager. 

After the sale we have service and maintenance interactions with the customer. 

Each machine we make has a serial number and each project is tracked by a work order (the initial build, maintenance and service all have individual work orders. 

Initially, I'm thinking of setting up projects as customers and add project builds, service and maintenance as individual issues. 

Any feedback would be appreciated as we want to be able to search a serial number and find any activity related to a particular machine. 

Thanks in advance for any feedback. 


1 answer

1 accepted

1 vote
Answer accepted
Ryan Fish
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.
Aug 14, 2018

@Darrell Smith

good luck setting it up, i did something similar in the past for a client. 

Board columns would match your manufacturing process (design/ fabrication/ QC/ Assembly/ UAT)

Issues followed this general path:

Epics = customer --> Features = (work) orders --> Stories = elements of order -->Sub-tasks = steps to achieve Stories

Change orders would generate a new story, significant changes might require a new feature. Service = new story. All should link to original story for reference and history.

Serial number/ machine line you could use the component field or labels. Component is better because it is a list v free text (label) to reduce clerical errors.

Hi Ryan ,

I would like to implement the same thing on a doors factory . How ever i would like to connect the Jira Software to our CRM that is managing the orders . 

What the requirements do i need to do so ? 

Hi @carlos nunes

just came across your goal & question related - how did it go? 


Like Roderick Prewitt likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events