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
Next: Root
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.
Hello, is there a best practices document for handling a multi vendor cloud integration project? My corporation is want to integrate with multiple vendor clouds so I created a Kanban board under 'Software Development' but feel this is too linear for this type of project.
Thank you, and appreciate any advise of help with this topic.
There's no best practices documents in terms of how to use Jira for project management. Are you looking to track integrations separately or together? Are they done by the same team? Is it your team that's managing the project?
Lots of questions to answer which will help determine what to do.
Jacob
Thanks, Jacob. Yes, our team is managing the project. The 'project team' consist of members from a corporation and members from various vendors running their cloud service. We are looking to track the integration together but I would like to isolate issues independent of the other system. I know I can use filters to isolate related issues, and that may be my solution. Not sure if this is the best direction though unless there is a 'better' alternative. Also, this is a Jira team project, not company project. I believe there may be limitations between team and company defined projects. Hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Using filters is a possibility as well as separating each vendor's integration or service as it's own Epic. You'd be able to group them all in a Kanban board, separate them by Epic and create dependencies for them.
Unfortunately, I'm not sure if there's a more elegant / easy solution and I can't think of any at the moment.
Jacob
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.