Add ways to lock DevOps iterations with the ability to move requirements between different operations.
Would make LucidSpark incredibly useful in the long run.
Add ways to lock DevOps iterations with the ability to move requirements between different operations.
Would make LucidSpark incredibly useful in the long run.
Hi Armando thank you again for contributing to the Lucid for Developers Community space. As the Azure DevOps integration is not built on our Extension API I’ve also moved this post to our Lucid Suite Community space.
Your suggestion about enhancing the ability to lock DevOps iterations and move requirements between operations is intriguing. To better understand and potentially implement your idea in the future could you provide more context? Specifically we'd love to hear about your use case and any specific scenarios you envision with the improved ADO/Lucid Cards integration. The more details you can provide the better we can tailor our solutions to meet your needs.
Thanks again for your valuable input and we look forward to hearing more from you!
So:
As my company works with Agile we tend to stick to sprints on a two weekly basis though sometimes some requirements/tickets get to move to the next sprint. Doing so within DevOps is quite simple:
through the menu for each requirement you have Move to iteration.
Dynamic matrixes within Lucid are not strictly of one or the other sprint and essentially each ticket belongs to itself within the matrix.
My idea is that it would be incredibly useful to have the ability to create sprint-locked dynamic matrixes and in that way moving a ticket from one matrix to the other would move that ticket from one to the other sprint also within DevOps.
I have no idea of how you would be able to implement it but one way could be to choose the whole sprint to display (and not each and every requirement) and add the function to drag/drop requirements from one to the other matrixes so to change their sprint within DevOps.
Thank you for taking the time to provide such a comprehensive explanation of your needs and vision for the ADO/Lucid Cards integration.
The concept of sprint-locked dynamic matrices in LucidSpark which can directly influence the iteration of a ticket in Azure DevOps is intriguing! The drag-and-drop functionality you've described would certainly streamline the process and enhance the user experience during sprint planning.
While I can't provide an immediate solution or timeline for this feature's implementation I've passed your feedback directly to our product development team. They are always eager to hear from users like you!
In the meantime if there are any other suggestions or feedback you'd like to share please don't hesitate to reach out. Thank you again for being an active member of our Community and for your continued support of Lucid.
Hi Armando! Abby here from Lucid. I thought you, and others who might come across this topic in the future, might be interested in Lucid’s Agile Trusted User Group. This group is made up of passionate, experienced users who regularly use agile methodologies in their work. As part of this group, you’ll have the opportunity to connect directly with Lucid’s product team and share insights about your workflows, pain points, and needs, shaping the future of Lucid’s agile tools. 🎉 You can learn more and apply here. Thanks!
A Lucid account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under age 18. You will be redirected to the Lucid app to log in.
A Lucid account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under age 18. You will be redirected to the Lucid app to log in.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.