Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can this be used to track unit serial numbers and assemblies serial numbers?

david_neal
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 16, 2020

We want to manufacture a unit that has multiple assemblies and many of those assemblies have several sub-assemblies. Along the way are several components that have serial numbers and the all of the assemblies have serial numbers. 

 

I want to build a issue for each sub assembly. It would list all of the parts we want to track in that sub. Then the next level up assembly I want to be able to pick which subs I have used. 

The top level is the unit where I have all the assemblies assigned to it. 

 

So if someone asks me which unit has circuit board xx I can tell them. 

And if we replace that circuit board xx with circuit board yy then it will be able to track that and the history. 

Will Jira do this? The old issueview did this just fine. 

 

Thanks

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 17, 2020

Hello @david_neal

Welcome to the Atlassian Community!

Per your description, I understand you're trying to add some hierarchical levels in your Jira Cloud site, however, I could not see clearly how many levels you are trying to implement and what features you are looking for.

Please, allow me to bring you some Jira features comparing with the description of your question to confirm we are on the same page here:

We want to manufacture a unit that has multiple assemblies and many of those assemblies have several sub-assemblies. Along the way are several components that have serial numbers and the all of the assemblies have serial numbers. 

Basically, Jira Cloud has three hierarchical levels:

Epics > Standard Issue types (Story, Task, etc) > Sub-tasks

Comparing with your description, you can fit the scenario you want with the levels above, mapping as Units(Epic), Assemblies (Standard issue-type) and sub-assemblies (Sub-tasks) properly.

About the components you mentioned, you can use the default fields to add them to your issues where you will be able to filter and return issues with specific components using JQL filters.

I want to build a issue for each sub assembly. It would list all of the parts we want to track in that sub. Then the next level up assembly I want to be able to pick which subs I have used. 

The information/link from the child issues is displayed in the Issue View of the parent issue.

In Epics, it is displayed in the "Issues in Epic" section:

Screen Shot 2020-04-17 at 19.01.11.png

In Standard Issue types, It is displayed in the "Subtasks" section:

Screen Shot 2020-04-17 at 19.05.24.png

Let us know if you have any questions or if I didn't provide one of the features you requested.

Suggest an answer

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

Atlassian Community Events