Join us on February 28th for our upcoming webinar to learn how Jira Service Management can help your team accelerate end-to-end incident resolution and collaborate across Dev, Ops, and support on one platform. Register here: https://lnkd.in/dsRuDiJR
Jira Service Management’s Post
More Relevant Posts
-
Looking forward to this one! 🌠4 ways to elevate incident response with Jira Service Management 🌠 Join this webinar to learn why companies are choosing Jira Service Management to lower costs and unite their Dev and IT Ops teams on one platform for faster resolution. https://lnkd.in/et_tSrNb
To view or add a comment, sign in
-
-
Feature flags can ruin your codebase: • They give PMs an excuse to 𝗻𝗼𝘁 𝗺𝗮𝗸𝗲 𝗵𝗮𝗿𝗱 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻𝘀, such as completely removing a feature. • The codebase becomes more complex and 𝗵𝗮𝗿𝗱𝗲𝗿 𝘁𝗼 𝗺𝗮𝗶𝗻𝘁𝗮𝗶𝗻. • 𝗧𝗲𝘀𝘁𝗶𝗻𝗴 𝗯𝗲𝗰𝗼𝗺𝗲𝘀 𝗵𝗮𝗿𝗱𝗲𝗿 (and lower quality) - figuring out what combination of feature flags needs to be supported. A Jira ticket for deleting them isn't enough. Luckily, you can do something about it! In his great article here: https://lnkd.in/dFDq2PeH Pete Hodgson talks about 4 types of feature flags: 1. Release toggles 2. Ops toggles 3. Experiment toggles 4. Permissions toggles Each type of toggle should live for a different period of time and have different requirements for changing it. Read my article for a deeper dive on how to deal with it: https://lnkd.in/d9VM4iBR
To view or add a comment, sign in
-
-
Some more Jira Service Management best practices? Yup! ✨ This time, let’s focus on Request Types: the things that help you get the information you actually need without info overload. 👏 We’ve got more JSM best practices coming soon. What do you want to learn more about? 👇
To view or add a comment, sign in
-
🔥 Issues grouping right from the scanner’s settings Use case: many CVEs for your project dependencies, which you can usually fix just by updating them now can be in only one Jira task https://lnkd.in/dUtpgXf5 #appsecurity #appsec #devsecops #appsdevelopment
To view or add a comment, sign in
-
-
Curious about tracking issue changes in Jira? 🤔🔄 Advanced Issue History offers a clear view of issue changes, including dates, authors, and field details. Ideal for audits and maintaining a transparent change log! 👨💻 🌐 Explore it now: https://lnkd.in/d_VPJT-4 #Sevidev #Atlassian #Jira #AdvancedIssueHistory #Productivity
To view or add a comment, sign in
-
-
🍿 🎬 Follow along as Brad Quirk walks through Dependency Mapper for Jira to show you how to get started quickly and visualize your dependencies https://lnkd.in/dAjX2AcE
To view or add a comment, sign in
-
Atlassian Jira users, have you been searching in Jira for a way to manage the technical risk of your Product Increments? You need Clear Path for Jira. Clear Path identifies the Critical Path of tickets that contain the most story points in your Product Increment. Ensuring a ticket on the critical path is picked up on the first day of the sprint mitigates the effects of realized technical risk and reduces your chance of your schedule slipping. Watch this 1 minute video to see how Clear Path can help you and your team manage your technical risk: https://lnkd.in/g-iR7MfN. #AtlassianJira #ClearPath #TutorialThursday #Forge #Moser Labs
4. Clear Path: JIRA App to Manage Your Technical Risk
https://www.youtube.com/
To view or add a comment, sign in
-
Knowledge bases in Jira Service Management. 📚 How can you, your team, and your customers get the most out of these gems? There’s so much you can do with JSM – are there any features you want us to do a deep dive on that we haven’t covered yet? 🤔 Let us know! 👇
To view or add a comment, sign in
-
Transforming Businesses through Cutting-Edge IT Service Management Solutions | Elevating Customer Success and Revenue Growth | ITSM | Jira Service Management | Cherwell
Are you tired of managing un-vetted backlog items? Jira Service Management is here to help! Join our webinar to witness how development teams are improving work intake, enhancing incident response, and ensuring compliance through automation. https://lnkd.in/gZNeNm8y
To view or add a comment, sign in
-
-
If you want metrics out of Jira, the single most important thing you need to access is the issue history and it’s not obvious how to get that. Just about all the metrics you’ll want to collect will need data from the history - you might need to know when an item started or when it entered a certain priority or when the flag was set or cleared. In this second part on the Jira API, I dig into the issue history. How do you get it, what can you expect to find there and more interestingly, what's not there that you really need. https://lnkd.in/g-cuFBmY
To view or add a comment, sign in