![]() They use it for discussions, sharing and editing documents, as well as questions and answers.įor example, team lead Anke uses our Microsoft Teams for Jira app from Microsoft Teams. Like a Scrum meeting, the team discusses priorities and deadlines, and decides what needs to be done this week.īesides doing project management in Jira, our Business specialists are Microsoft Teams power users. The team bases the weekly planning meeting on Jira, to get an overview of what team members are working on. Our Business team, which is responsible for marketing, partner management and HR, also uses the new app. Not only can they see the conversation there, they also get an overview of the entire Jira issue. At the same time, his colleagues don’t have to open JSM – they can just keep using Teams. Timur can stay in Jira Service Management the whole time, as messages from his colleagues who use Teams just pop up in the Jira issue. He posts both the issue and his suggested solution to the appropriate Teams channel. He uses Microsoft Teams for Jira to start a Teams conversation right in the Jira Service Management Issue. Now Timur wants to get the team involved and discuss his ideas for the feature. First, he does a rough appraisal himself, and soon sees a way to implement it. One of our developers, let’s say Timur, who is heavily involved in our Confluence products, sees a customer feature request about Outlook Meetings for Confluence in Jira Service Management. That’s when we rely on our expertise as a team. However, we occasionally get interesting suggestions, or problems that are not so easy to solve. Sometimes, it is a simple question about installation or a minor bug that we can sort out in the next release. We have various product teams who are responsible for developing new features, as well as responding to and resolving customer issues. Our developers also provide support for our apps using Jira Service Management. Instead, we strive to develop deep integration and offer users true functionality, adding real value.Īt yasoon, both the Developer and Business teams use our Microsoft Teams for Jira app. If the only end result is that one tool sends a few more notifications to another, nothing has been gained. We work with both Microsoft Teams and Jira ourselves, and have to admit: our customers are right.Īt yasoon, we don’t just want to connect random tools because we can. Many of our customers weren’t happy with the functionality of the existing apps connecting both tools. That was certainly the case for our new Microsoft Teams for Jira app. If we see more requests for certain features and apps, we add them to our roadmap. ![]() We always say that we develop the new apps and features our customers need and want. The app currently works with JFrog Platform cloud accounts and Atlassian cloud accounts. When you view an issue in Jira, an additional widget lists and hyperlinks to the resolving builds in Artifactory. The JFrog Artifactory app for Jira enables a complementary facility in the Jira Cloud dashboard. Build pipelines should collect this data from Git and add it to the build information metadata in Artifactory that provides a traceable path to component binaries and the conditions for deterministic builds.Īs a standard feature of Artifactory, the referenced Jira issues for each build are then listed in its build info display in the Artifactory dashboard, with hyperlinks to the Jira dashboard. Disciplined developers tag each Git repository source code check-in with the Jira issue key(s) those changes resolve. The app leverages Artifactory’s ability to collect issue key messages from Git, and log them with your builds. The JFrog Artifactory app for Jira adds relevant build information metadata from Artifactory to your Jira Cloud dashboard, so developers viewing an issue in Jira can readily identify and view the build in Artifactory that fixed it. That’s the DevOps pipeline principle behind the JFrog Artifactory App for Jira, which forges a traceable link between your issues in Atlassian Jira Cloud and your builds in Artifactory on the JFrog DevOps Platform for cloud. The path between two clouds ought to be a speedy two-way street.
0 Comments
Leave a Reply. |