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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

Need to use project as main task and then sub-project

To use jira we need to have main projects and under them sub-projects, each sub-project will have entries of multiple team members. For example, we manage Technology Development, under this main project or activity we have multiple projects for each product, each product has four main components, electronics design, mechanical design, software design and finally assembly and documentation.  The process repeats for each project or product or sub-project under the Technology Development main project. So far I have not been able to find the way to do this simple structure, it seems there is only one way to manage Jira, multiple projects and then tasks. This is complicated when we have multiple projects and sub-projects and we try to keep track and the system organized.

1 answer

1 vote

Hi @Juan_Torne_Sr

I'm not sure I have the full context. Is your Jira instance for Technology Development only, or is is shared by other departments?

One thing you could do is to use Epics for the main projects under Technology Development and use Jira components for the five that your mentioned: electronics design, mechanical design, software design, assembly and documentation. When linking tasks to epics it makes it really easy to filter. And by having components you could also assign component owners or leaders, which is a neat feature.

Let me know if this model wouldn't work and I can try to re-adjust.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
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...

226 views 7 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