Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

HELP! Different Development Teams Different Ticketing Methods -- I need a workable solution PLEASE

Flo Kistner
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 14, 2018

Hi I'm a program manager who was recently brought into an past due project and this project involves working with several different development teams.  Each development team has their own ticketing system either in JIRA or in TFS.  What we now have are multiple development tickets and efforts going on and teams only have visibility on their tickets and work items.  What is the best way to capture everyone's ticketing methodology so that a) everyone has visibility on what the other teams are developing (maybe some synergies can form) b) we don't run into duplication of efforts that don't integrate across the entire project and c) the business can make better and informed decisions on what they feel are most important i.e. specific bug fix or enhancement or ???  Help!  My first suggestion was to create a table w/four individual columns (one column per each of the development teams) and then input the JIRA or TFS ticket number, title, description, level of effort/points but that's going to be very time consuming and riddled with opportunities for human error -- please does anyone out there have any suggestions or templates?  Thank you so much!  

1 answer

0 votes
Kit Tin Mak February 22, 2019

Hi Flo,

I think our solution TFS4JIRA might help in your case to synchronize the issues and workitems so you can see all the information and fields in both sides.

 

You may check our solution at the link below,

https://spartez.com/products/tfs4jira

https://marketplace.atlassian.com/apps/42296/tfs4jira-synchronization-and-migration?hosting=server&tab=overview

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events