SOLVED

An index of DevOp items posted in a Team

%3CLINGO-SUB%20id%3D%22lingo-sub-2474404%22%20slang%3D%22en-US%22%3EAn%20index%20of%20DevOp%20items%20posted%20in%20a%20Team%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2474404%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20customer%20making%20use%20of%20the%20DevOps%20compose%20extension%3C%2FP%3E%3CP%3E-%20now%20they%20can%20browse%20an%20item%20from%20DevOps%20and%20post%20about%20it%20and%20have%20a%20conversation%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProblem%20is%20that%20a%20week%20later%20someone%20else%20will%20browse%20the%20same%20item%20and%20create%20a%20new%20post%20about%20it%20(they%20may%20not%20know%20it%20already%20has%20been%20posted%20about%2C%20or%20find%20it%20futile%20searching%20for%20it)%3C%2FP%3E%3CP%3E-%20ie.%20there%20are%20now%20two%20posts%20about%20the%20same%20item%3C%2FP%3E%3CP%3E-%20but%20there's%20no%20place%20where%20all%20posts%20about%20the%20same%20item%20are%20collected%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'd%20like%20to%20see%20an%20index%20of%20each%20DevOps%20item%20in%20Teams%20that%20has%20been%20posted%2C%20and%20when%20I%20click%20on%20one%20-%20it%20shows%20me%20the%20posts%20that%20have%20been%20made%20about%20it%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20solution%20I%20can%20think%20of%20now%20is%20to%20not%20use%20the%20DevOps%20integration%20and%20use%20Microsoft%20Lists%20instead%3C%2FP%3E%3CP%3E-%20this%20way%20we%20get%20an%20index%20of%20each%20item%20and%20just%20the%20one%20conversation%20about%20each%20item%20(but%20this%20may%20be%20limiting%20if%20you%20want%20multiple%20posts%20about%20each%20item%2C%20for%20example%2C%20to%20talk%20about%20sub-components)%3C%2FP%3E%3CP%3E-%20but%20it%20feels%20like%20unnecessary%2Fduplicate%20work%20to%20'create%20an%20item%20in%20Microsoft%20List'%20for%20each%20DevOps%20item%20we%20want%20to%20talk%20about%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2474404%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2496290%22%20slang%3D%22en-US%22%3ERe%3A%20An%20index%20of%20DevOp%20items%20posted%20in%20a%20Team%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2496290%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F61715%22%20target%3D%22_blank%22%3E%40John%20Tropea%3C%2FA%3E%26nbsp%3B-%26nbsp%3BThis%20is%20not%20possible%20using%20existing%20of%20Azure%20DevOps%20integration.%20However%20you%20can%20build%20what%20you%20are%20looking%20for%20using%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fplatform%2Fmessaging-extensions%2Fwhat-are-messaging-extensions%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EMessaging%20Extension.%26nbsp%3B%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

I have a customer making use of the DevOps compose extension

- now they can browse an item from DevOps and post about it and have a conversation

 

Problem is that a week later someone else will browse the same item and create a new post about it (they may not know it already has been posted about, or find it futile searching for it)

- ie. there are now two posts about the same item

- but there's no place where all posts about the same item are collected

 

I'd like to see an index of each DevOps item in Teams that has been posted, and when I click on one - it shows me the posts that have been made about it

 

The only solution I can think of now is to not use the DevOps integration and use Microsoft Lists instead

- this way we get an index of each item and just the one conversation about each item (but this may be limiting if you want multiple posts about each item, for example, to talk about sub-components)

- but it feels like unnecessary/duplicate work to 'create an item in Microsoft List' for each DevOps item we want to talk about

1 Reply
best response confirmed by Wajeed-MSFT (Microsoft)
Solution

@John Tropea - This is not possible using existing of Azure DevOps integration. However you can build what you are looking for using Messaging Extension.