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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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
Highlighted

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

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?)

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
TAGS

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