![]() Ready for production use with associated SLA and technical support obligations. We have shipped an early version, and we are gathering feedback. We have decided to build this feature, but are still figuring out how. We hope this makes it easier for you to understand what’s happening with Azure DevOps and what is coming up.įeature in the discovery phase. So, we are adding more states to the feature workflow and making those states visible on the timeline. Additionally, the states we currently have, which are “ Planned,” “ In Progress,” “ Closed,” and “ Cut” don’t cover all the stages of a feature’s lifecycle. The current features timeline lacks a state column for features, which requires you to leave the page to check the status of each individual item. This time around, we’re also making some changes to the process itself, and we want to share those with you. With each quarterly blog update, we bring you a list of enhancements we’re making to Azure DevOps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |