2 min read

Praecipio Consulting’s Innovative AI-Powered App for Jira Cloud: Intelligent Image Classifier

By Praecipio Consulting on May 31, 2022 10:51:43 AM

blogpost-display Image-herro_Blog - Image Classifier

As machine learning and artificial intelligence continue to transform the way we use our technology platforms, the potential for innovation skyrockets. Praecipio Consulting’s Intelligent Image Classifier for Jira Cloud takes Jira’s existing automation to the next level through intelligent image recognition. Developed as part of Atlassian’s global Codegeist hackathon using the revolutionary Forge development platform, Intelligent Image Classifier enables teams by bringing the power of artificial intelligence to Jira. 

Award-winning App Combines AI and Automation to Boost Service Quality

With Intelligent Image Classifier, teams are able to automatically classify issues using multiple artificial intelligence algorithms, based on the AWS Rekognition platform. The app improves user experience in searchability, automation, and issue classification by filtering based on detected text or content within an image attached to a Jira ticket.

When asked about the origins of Intelligent Image Classifier, VP of Software Services Phil Maddaloni said, “Given our work with machine learning and AWS and our dynamic expertise within the Atlassian ecosystem, it was a perfect fit for us to apply these skills in a way that would add significant value for end users.”

Praecipio Consulting has discovered many use cases for the Intelligent Image Classifier, but the initial need was brought to the company by a local municipality. This customer wanted to improve service to their residents by identifying certain types of “work items” within their town, and classifying them based on content attached to tickets submitted through their Jira Service Management portal.

Improved Customer Service through Intelligent Image Classifier

We’ll explore a common application of this app with the story of Mrs. Smith and her cat, Mittens:

Mittens climbed the tall oak tree in the backyard, and now she’s stuck! Mrs. Smith quickly takes action, snapping a picture of Mittens and submitting a ticket with the picture through the municipality’s Jira Service Management platform. Intelligent Image Classifier automatically starts processing information. The app scans the picture of Mittens and recognizes the animal, even picking up text from a nearby street sign and adding that to the ticket. It automatically assigns the ticket to Animal Control’s service desk. Animal Control immediately dispatches a vehicle to the scene to rescue Mittens. Intelligent Image Classifier saves the day, streamlines the process, and Mrs. Smith is a happy citizen.

Later, the municipality completes an annual review of how its Animal Control department performed, and how many calls were serviced. To do so, an Atlassian administrator quickly and easily searches keywords like “cat”, “dog”, “animal”, “coyote,” etc. to find how many issues were automatically tagged with these keywords.

Future Uses with Image Recognition

In addition to image recognition and issue tagging, Intelligent Image Classifier can scan images for file types and integrate with Jira’s existing automation to incorporate into issue filters and customize Agile boards. Soon, the app will be able to automatically hide detected specific content based on targeted words and images. These use cases all improve overall user experience and security.

Praecipio Consulting is dedicated to developing innovative software for our customers, and we are excited to be recognized for our Machine Learning and Artificial Intelligence capabilities by one of our most innovative and foundational partners, Atlassian. To learn more about how Praecipio Consulting can help your team propel innovation through exceptional software development and custom apps like Intelligent Image Classifier, contact us today!

Topics: automation artificial-intelligence marketplace-apps jira cloud
3 min read

4 Things to Look Out for When Migrating to Atlassian Cloud

By Jerry Bolden on Jun 28, 2021 3:17:41 PM

2021-q4-blogpost-Challenges moving from server to cloud

Migrating to the cloud can be a challenging move for any organization: there are many moving pieces to keep track of, and with the threat of negatively affecting both internal and front-facing operations, failure is not an option! Here are some key blockers to keep in mind when migrating to Atlassian Cloud from on-premise instances, so that you can review ahead of time just how prepared for a successful migration your company is:

  • User Management
  • Automations
  • Size of Attachments
  • Apps

User Management

User Management and how users are set up is a major difference when operating in Atlassian Cloud versus on premise. This is an important obstacle to understand and address, as the approaches for user management are different between cloud and on-premise. Key to this is how users are created and managed; equally important is identifying any users with missing or duplicate email addresses, since these cause problems with data integrity and users being able to use Filters and Queues in Atlassian Cloud. 

Automation

Automations are critical to research, as some automations may not be functional or even allowed in Atlassian Cloud: these will need to be identified and assessed to determine the balance between the value they bring and the level of effort of recreating them. 

Attachments

Size of Attachments becomes critical when using the Jira Cloud Migration Assistant, as this does not support migrating Jira Service Desk projects, which may require importing data via Site Import that forces attachments to be uploaded separately in 5 GB chunks, one chunk at a time. This alone will drive the migration of attachments to exceed a typical outage window, as the Site Import process must first conclude prior to uploading attachments. 

Jira Service Management utilization is tied to the size of the attachments as noted above. While JSM is used heavily it is currently not able to be migrated using the Jira Cloud Migration tool. With that being said this drives the use of site import. With this comes having to migrate the users and attachments separately. This becomes more moving parts during the migration outage and the coordination and timing will become even more critical.  

Apps

Jira Suite Utilities (JSU) / Jira Miscellaneous Workflow Extension (JMWE) / Scriptrunner are apps available in the Atlassian Marketplace that may be used in one or more of your current workflows. While these apps have helped to drive the creation of workflows and processes to automate certain transitions or enforce proper data collection, there is also no current migration pathway to Atlassian Cloud. While JSU has become part of the native cloud, JSU along with the other two apps must be manually fixed in all workflows migrated up to the cloud. You must run a query on your on premise data base to ensure you map out all transitions affected by the apps. Then once the migration to cloud is complete, they must be reviewed and recreated manually to ensure they are all working properly. Where possible utilizing the out of the box options, that mimic JSU, can help to move away from at least one app. 

Specific to Scriptrunner, one common scenario is the use of it in filters can cause them to no longer function, potentially causing boards and dashboard to render incorrectly. These filters must be rewritten using the Scriptrunner Enhanced Search functionality. One good example is any filter that contains the phrase "issueFunction not in" will need be rewritten as "NOT issueFunction in". It would be advisable, when doing the migration to Cloud, to open a ticket with the vendors for advise on how to fix scenarios with JQL that worked in Server/Data Center that no longer work "as-is" in Cloud.

Overall these key obstacles will get you on the correct path to understanding what you know will need to be done in preparation for starting the migration. This by no means is a complete list of the only obstacles that you can encounter, but we hope it will help you to be proactive in fixing obstacles before they become a blocker to the migration.

We are Atlassian experts, and understand how the move to cloud can be fraught with unpleasant surprises. If you have any questions, or are in need of professional assistance, contact us, we would love to help!

Topics: atlassian blog automation best-practices migrations atlassian-cloud marketplace-apps jira-service-management cloud migration
4 min read

Why Upgrade Your Atlassian Stack?

By Suze Treacy on Apr 16, 2021 11:18:00 AM

Blogpost-display-image_Why Jira-Confluence upgrades are importantOne key component of managing your Atlassian products is managing their upgrades. Upgrades can present a daunting and significant time investment for many companies, generally involving apps, custom-developed plugins, and integrations, with a large number of users dependent on their success.

You know what upgrades are and that they're important. So why am I talking to you about them? Imagine the scenario, you're busy, you haven't had a chance to check in on the latest Atlassian security vulnerabilities and the emails you've received about them have been missed. You have also had higher priority work eating up team time, which has prevented the planning and execution of your Atlassian upgrades. One day, your instance comes under attack through one of the vulnerabilities exposed in the CVE. Your data is potentially exposed. An urgent, large, expensive, complex effort ensues in order to secure the instance; after 3 days, 2 full sweeps of the instance and multiple upgrades, the vulnerabilities are mitigated and your instance is safe.

Are you confident in when your applications are due an upgrade? Let's review a few common reasons why an upgrade may be recommended:

End of Life Policy

Once Atlassian has released a major feature version, it, and all iterations related to that major version, are supported for two years. After that, the versions are considered End of Life, and you will no longer receive support from Atlassian for any issues which arise. It is when reaching this point, that many people start considering upgrading their instances.

Security Vulnerabilities

Every Wednesday, Atlassian releases any new security vulnerabilities which have been identified for their server/data center products. These vulnerabilities include a security level, which is based on an Atlassian-calculated CVSS score for each vulnerability.

Severity Rating System followed by Atlassian:

Atlassian_severity_rating_system

Although there may be opportunities to mitigate security vulnerabilities in your current version, it is recommended to patch or upgrade immediately when a Critical vulnerability is identified. Vulnerabilities with a critical score generally result in root-level compromise or servers or infrastructure devices, or are straightforward to exploit.

Current security advisories can be found here:

https://www.atlassian.com/trust/security/advisories

New Functionality/Capabilities

Did you know that there is a new feature release for Jira Software every 6 weeks alone? Atlassian encourage users to submit bugs and feature requests at jira.atlassian.com. This public forum allows users to vote for and comment on submitted issues, and the Atlassian team utilize this and other feedback as a factor in their decision for what to implement next.  Platform releases contain the most significant changes, while Feature releases contain new features, changes to features, changes to supported platforms and removal of features. Feature releases can be designated as Enterprise releases, which, generally designated annually, are preferred for companies who need time to prepare for upgrades, but still want to receive critical bug fixes.

Compatibility with other Server Components

From time to time, Atlassian add and deprecate support for other server component platforms which work alongside your Atlassian application. For example, did you know that in Jira Software 8.6 and Jira Service Desk 4.6, support was added for PostgreSQL 10 and deprecated for Internet Explorer 11, whereas in Jira Software 8.8 and Jira Service Desk 4.8, support was deprecated for Microsoft SQL Server 2012 and PostgreSQL 9.4 & 9.5. To ensure optimal operation of your Atlassian instances, it's just as important to upgrade components of your server architecture, as well as your instances themselves.

Plugin Support

If you are one of the many teams who utilize plugins within their Atlassian applications, plugin compatibility and support is another area to be aware of when considering upgrades. Has support been deprecated for the plugin with the Atlassian version you're running? Is the plugin still supported when you upgrade to your target version? Atlassian have developed the Universal Plugin Manager, available in both Jira and Confluence, to enable you to screen for any compatibility problems prior to starting your upgrade. There are 4 categories for Compatibility which plugins can fall into - Incompatible (the plugin is not compatible with the target version), Compatible, Compatible if updated (the plugin is not currently compatible, but will be once running the compatible version), and Compatible once both are updated (the new version of the plugin isn't compatible with your current instance version - you need to upgrade your instance prior to updating the plugin).

Unable to Skip a Platform Release

When considering which version you'd like to upgrade to, it's important to consider your current version and your target version. When upgrading, it is not possible to skip a platform release - therefore, for example, when considering a Jira Software upgrade, it is not possible to jump from a 6.X release to the 8.X release and skip the 7.X release, you would need to take an intermediate step to upgrade to a 7.X version. Due to the functionality changes being much greater between platform releases which are not adjacently sequenced, there are more edge cases, and thus, greater risk, when navigating an upgrade spanning multi platform releases.

For assistance with upgrading your applications, partner with Praecipio Consulting's Managed Services team! Our team, fully dedicated to the Atlassian stack, offer peace of mind through managing, supporting, and maintaining your Atlassian tools, enabling you to maximize the benefits of your Atlassian applications while allowing your team to focus on their core roles. Working with our Managed Services team offers tribal knowledge and best practice from over 10 years working in the tools, allowing us to enable your Atlassian stack is optimized and operating at peak performance.

For more information on Managed Services, or anything else Atlassian related, contact us, and one of our experts will be glad to talk with you.

Topics: blog managed-services marketplace upgrade version-control-system atlassian-products marketplace-apps
2 min read

The Impact Installing Apps Can Have on an Atlassian Application

By Chris Hofbauer on Mar 30, 2021 1:30:00 PM

Blogpost-display-image_The impact of apps on an Atlassian applicationPerformance and uptime are crucial when hosting any application. For the Atlassian suite, the use of apps can have a major impact on these hosting aspects. There are many third-party developers as well as Atlassian developed apps that are available to be installed within the Atlassian tech stack. Depending on the app installed, each of these apps will have its own impact on the application and its health. Many apps that may be installed are considered lightweight and the impact would be very minimal; however, there are apps that are resource intensive and can cause significant impact of application performance. The apps that tend to cause the largest impact on application performance are those that allow customization of scripts and manipulation of data within those scripts, especially if these scripts are capable of running on a particular cadence or during certain issue functions. Other app types that are frequently found as the culprit for performance issues are those that return long running database queries. Common impacts from these resource intensive types of apps are high CPU usage and high memory usage. When either of these metrics begin to rise, the server is forced to work harder in order to operate the application, which then can cause the application to face performance degradation, manifested in slow page loads, timeouts, or outages. 

There are best practices you can implement in order to prevent your apps from having an impact on your application's performance. It is highly recommended that you install apps that are supported and developed by a trusted developer. Be sure to also read any documentation and truly understand what the app does before installing. It is extremely important that the apps are always up-to-date as well: apps may have bug fixes in releases that are ahead of yours, and even though you may not be currently facing any issues with your release, it is best to be sure you are on the latest version so that you can prevent any issues that may already be known by the developers. We also recommend that you thoroughly test any app you are considering installing within a non-production environment. Running User Acceptance Testing in a lower environment will allow you to capture any performance issues that may come from the app. Following this approach will strengthen your instance and help prevent any potential impacts your apps can have on your Atlassian applications.

If you run into any trouble with your Atlassian apps, let us know, we'd love to help you make the best of your tools.

Topics: atlassian blog best-practices hosting marketplace-apps
3 min read

How do I migrate to Cloud if my apps aren't compatible?

By Jerry Bolden on Dec 23, 2020 1:06:11 PM

Blogpost-display-image_How do I migrate to Cloud if my apps arent compatible-

How many people are ready to move to the new hotness: Atlassian Cloud?  While this is becoming a more focused platform for Atlassian, there are some things that each company/team will need to think about as they move to the cloud:

1. What do I do if my current Server/DC apps are not compatible? 

2. What do I need to understand about my current set up within my workflows?

Apps are used to upgrade the out-of-the-box abilities of Jira, Confluence, and Bitbucket and most people not only become reliant on the apps, but may not even know they're using the apps for their day-to-day work. While there are quite a few apps operating on all three platforms (Cloud, Data Center and Server), some apps may not be available for all three platforms. For example, an app may be supported for Cloud-only or Data Center only.

While trying to migrate to Cloud, you need to understand which Apps are also compatible in Cloud and which ones are not. You can navigate to Atlassian Marketplace and set your first filter for Cloud.  Then, simply search the App name and the marketplace will do a good job giving you other options that have some of the same features as your current Data Center/Server app. Look through the recommendations and compare the current features you use with some of the recommended apps features.  The best thing is to also download a trial version of those apps in Cloud, but also if you are still on Data Center/Server, see if they have an app trial for those platforms as well.  

The other side of this will be having apps that exist on Cloud as well as on Data Center/Server but may affect your workflows.  For example, Automation has come included within the cloud, but JSU Automation Suite for Jira Workflows exists as a separate app on Data Center/Server.  While this app is now integrated into the Cloud,  when importing the data, workflows, etc. during the migration, you currently cannot use the Atlassian Cloud Migration tool and the links to the automation can fail. 

Reach out to those specific App vendors for support and open a ticket to understand what the migration path could be from Data Center/Server to Cloud. For example, In JSU's case, you have to redo all the affected workflows and their validators, conditions and post functions.  While some applications will be compatible, others will either require a little manual reconfiguration or finding ones similar in features to your current Apps.

Migrating to Atlassian Cloud is becoming more and more seamless as Atlassian continues to focus on the Cloud platform. But where apps are concerned, you will need to either find apps that already have a Cloud version or look for the Developer to review similar options and features. 

If you need guidance with your Atlassian Cloud migration, Praecipio Consulting is here to help! Contact us and one of our specialists will contact you shortly, and in the meantime, here are some helpful resources that you can start with

Topics: atlassian blog migrations cloud atlassian-solution-partner marketplace-apps
5 min read

Jira Align vs. Advanced Roadmaps: The Difference

By Amanda Babb on Sep 15, 2020 10:00:00 AM

Jira Align Adv Roadmaps Blog Header

As organizations continue to scale Agile practices, our team at Praecipio Consulting is frequently asked which Atlassian product will best support the effort. Principal Consultant, Brian Nye, put together a great webinar describing the differences between Advanced Roadmaps for Jira (formerly known as Portfolio for Jira) and Jira Align. As Praecipio Consulting has expanded our Jira Align practice, we'd like to take a moment to compare and contrast these products to help guide you in making the right decision for your organization. 

Your Agile and Digital Transformation Journey

Your organization can't talk about your Agile transformation without talking about your digital transformation and vice versa. After all, the Atlassian products are meant to support Agile frameworks as well as your digital transformation. Many organizations have embraced remote work as a result of the global pandemic and have fundamentally shifted toward online planning, road mapping, and execution management. 

Your organization may also use non-Atlassian applications to manage planning and road mapping. You've chosen to integrate these products with Atlassian for execution management. While this may be a great solution in the short term, I challenge this as a long-term solution. Many of the frameworks guiding agile-at-scale exist because we're trying to bring strategic planning closer to actual execution and back again. Ask your organization the hard question: does maintaining these integrations follow the organization's digital technology vision for the future? 

Advanced Roadmaps for Jira (formerly Portfolio for Jira)

Available as an App for Data Center/Server Deployments and packaged with Jira Software Cloud Premium, Advanced Roadmaps for Jira (Advanced Roadmaps) is a great way to bridge the gap for small- to medium-sized organizations. If you currently have fewer than 500 agile team members executing their work in Jira Software, Advanced Roadmaps for Jira can provide visibility within and across teams. First, define the hierarchy above the Jira Software Epic. We use Initiative most frequently when deploying this for customers because of the reference documentation from Atlassian. However, you can choose whichever naming convention you'd like as long as there is a corresponding Issue Type. For example, create an "Initiative" Issue Type and link it to a Hierarchy level in Advanced Roadmaps called "Initiative." We also strongly recommend the Initiative Issue Type live in a separate Jira Project from all other execution work. This helps your Agile teams focus on the current backlog of work while the Initiative moves through its own review, decision, and backlog refinement process. 

Creating a Plan is as simple as defining your source data (Jira Projects, Boards, or Filters), tying the sources to Teams, and choosing Releases from your source data. Honoring the Iron Triangle of project and program management, you may either choose to have the Plan dictate your schedule or, when planning for the next business quarter, you may choose to drag and drop the Gantt-style bars to schedule work. There is also an option to blend the calculations. Meaning, if a Sprint already exists and is pre-filled, let the Scrum Board be the source of truth. Have the Plan calculate any Empty Sprints going forward. The same is true for Releases and Teams: the Plan can auto-schedule a Team or a Release based on the relative rank of the backlog in the Plan. 

If you're looking to understand the impact of shifting priorities, you can enable Scenarios in a Plan. This will allow you to pull the source data from Jira Software and blend it with additional planning while maintaining the current execution schedule. You can add new Initiatives, Epics, and Stories, as well as adjust Release Dates, and observe the impact of adding, removing, or reassigning Teams to work. If you have the Server or Data Center App, you can group Plans together into a Program to understand the overall health of multiple Plans and Releases in a single view. 

Jira Align

As its name implies, Jira Align brings strategic planning and execution together in a single product. Pulling execution data from Jira Software and blending it with Agile-at-scale frameworks, Jira Align ties your strategic vision to tangible work and is best suited for organizations with more than 500 Agile team members executing their work in Jira Software. Instead of trying to define a hierarchy, Jira Align provides a pre-set hierarchy with flexible language. Whether you're running SAFe, LeSS, Scrum@Scale, or your own model, Jira Align's seamless integration with Jira Software provides visibility across multiple Portfolios and Programs. 

Jira Align comes in three deployment options: multi-tenant Cloud, single-tenant Cloud, and on-premise. While we recognize the allure of an on-premise solution, Praecipio Consulting recommends either the multi-tenant or single-tenant Cloud deployment. This provides the robust functionality of the product without the additional IT infrastructure management as well as managing routine maintenance such as upgrades. Jira Align also comes in two licensing models, Standard and Enterprise, billed monthly per user. Standard provides your organization the ability to run Programs (also known as teams of teams) whereas Enterprise adds the Lean Portfolio Management and financials into the mix. In addition, each Jira Align seat comes with four Jira, Trello, or integrated users. Another key difference between the two license levels is integration. With Standard, you can integrate a single instance of Jira Software with Jira Align. This is perfect for the organization that is large enough but lacks maturity in their Agile-at-scale framework. Enterprise provides unlimited connectors, which in the case of some of our clients, allows them to avoid the pain of merging multiple instances of Jira Software before deploying Jira Align

The Jira Software Epic is the lynchpin of the integration. Teams will still work with Epics, Stories, and Sub-Tasks within Jira Software whereas Product Managers, Release Train Engineers, Portfolio Managers, and Executives work within Jira Align. The robust permissions within Jira Align also focus the right role in the right data. A Program Manager may care about the execution of the program, whereas the executive wants to understand how you're tracking to the annual corporate strategy. By aggregating and rolling data upward, Jira Align provides health and status monitoring of quarterly, yearly, and long-term goals. With over 180 out-of-the box reports, every role at every level can access the right information at the right time to ensure your organization's success. Jira Align also has Enterprise Insights, an optional App, to take business intelligence to the next level. 

Which one is right for my organization? 

The first questions to answer while you're evaluating either tool are around Agile transformation maturity, digital transformation maturity, and user discipline both across and vertically in the organization. Because both options rely on teams to perform their execution work consistently and with good data integrity, either product can be a blessing or a curse. 

  • How long have your Agile teams been executing within an agile framework? 
  • How long have your Agile teams been executing within Jira Software? 
  • How consistent are your teams across the organization? 
  • Do your teams and your business understand one another and communicate well? 
  • How well has your Jira Software instance been governed since it was deployed?
  • How much chaff do you have in Jira Software? 

While this is not an exhaustive list, implementing either Advanced Roadmaps for Jira or Jira Align requires you to ask tough questions of your organization. Praecipio Consulting can not only help you assess your current state, but we can also provide guidance and recommendations to accelerate your digital transformation. If you are ready to take the next step in your digital transformation and Agile journeys, let's chat!

Topics: scaled-agile jira-align agile advanced-roadmap marketplace-apps
2 min read

SAFe Cheat Sheet: A Guide to Scaled Agile Framework

By Erin Jones on Feb 23, 2015 11:00:00 AM

No matter the size of your organization or your industry, the end game of any company is to deliver the highest quality product to customers at the greatest market value, with the lowest cost of production. This school of thought drives the Agile methodology of software development, pushing for faster delivery of better products with the least amount of risk, and has fueled the scalable Agile solution for enterprise-level organizations: Scaled Agile Framework (or SAFe). Operating under the principles of Agile development, SAFe aligns the development and initiatives of all levels of the enterprise company- from agile teams to executives- for accelerated value delivery at a reduced risk. Leveraging short feedback cycles organized into sprints and release trains, the cost of deployment decreases as deliverables have clearer direction and requirements to ensure a better fit for purpose. 

How does Atlassian support SAFe?

How does Atlassian support SAFe?

What are the core values of SAFe?

What are the core values of SAFe?

 

How does Atlassian support SAFe?

The Atlassian product suite was created (and is continually innovated) to support best practices in the Software Development Lifecycle. To that end, the use of products like Jira Agile, Confluence and Jira Portfolio integrate to bring maximum traceability to every release, enabling teams to hit their deadline and their budget with the highest quality product. With Atlassian, you unlock the power of SAFe, leveraging Jira Agile, Confluence and Jira Portfolio to achieve the following objectives (and much more): 

How does Atlassian support SAFe?

Want to learn more about SAFe?

Ready to learn more about how Scaled Agile brings best practices and delivers the greatest results to your enterprise organization? As Atlassian Platinum Solution Partners, Praecipio Consulting is here to help! 

First, check out our webinar on SAFe®, Agile in the Enterprise, presented by Senior Solutions Architect, Certified Scrum Master, and SAFe® Program Consultant Amanda Babb to get a more complete introduction to implementing Agile practices at the enterprise level.

Next, contact us today to see how our Consulting Services can help you meet your goals.

Topics: jira atlassian scaled-agile best-practices confluence enterprise sdlc jira-software safe marketplace-apps

Praecipio Consulting is an Atlassian Platinum Partner

This means that we have the most experience working with Atlassian tools and have insight into new products, features, and beta testing. Through our profound knowledge of Atlassian environments and their intricacies, we can guide your organization as you navigate these important changes.

Atlassian-Platinum-Solution-Partner

In need of professional assistance?

WE'VE GOT YOUR BACK

Contact Us