You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
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