Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

0 votes
Answer accepted
Ryan Fish Community Leader 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? 


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

172 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you