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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,559,661
Community Members
 
Community Events
185
Community Groups

Recommended Setup? Product Team?

Hi everyone!

We are currently reevaluating the tools we use at our company and attempting to move all teams over to Jira Cloud.  Of course like most other companies, we seem to do things differently than everyone else!

Questions for you all...

We have a product management team that will be the first "gate" for any new feature requests.  Then we have the development team who will be working in Jira Software.  The dev team is split into multiple different teams as we have multiple applications with front end and back end support.

We are B2C but currently our clients will not make product feature requests themselves.  They request of their client team who then validates the requests and submits them separately to product.  Once product researches and approves, then product opens the correct stories, etc for development.  The original request to the product team does not need to be a proper user story.  That comes later. 

If building each dev team as separate Jira Software projects... then what should the Product team be built as?  Should it be a Service Desk or a Software project that then will "Move" Items or "Link" to items in the dev proejcts?

Thanks in advance.

1 comment

Manuel Bastardo Castellano
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.
Jul 09, 2019

If your clients not make direct request you can use a jira software product. Using issue types, components, versions ....you should cover all the requisites.

So if the team opens items to the Product team, they won't always be expected to define what applications or an idea could cross multiple applications.  Then Product team evaluates the items to decide whether to pursue them or not.

If product decides to pursue them, would you think we just need to open all new items under the different application projects and then link them to this product item (the one the requester will be checking?)

Manuel Bastardo Castellano
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.
Jul 09, 2019

Hi Erin there is not a "unique or perfect way" to organize your jiras project you should customize to your teams process in jira.

But if you invest some time checking this topics before set up your jira and i m sure that you will have great results

How to define your Jira project

How to structure your Jira project

Agile Epics: Definition, Examples, & Templates

Team playbook.

 

Good luck..

Comment

Log in or Sign up to comment