Tag: Jira software

  • Atlassian Looks to the Cloud

    Atlassian Looks to the Cloud

    As part of an effort to accelerate migrations to the cloud, Atlassian is making instances of Jira Software, Confluence, Jira Service Desk and Jira Core running in the cloud available for free, as well as premium options that provide access to the same software with access to additional features and support.

    Harsh Jawharkar, head of go-to-market for Cloud Platform at Atlassian, said it’s apparent most organizations want to shift from on-premises to cloud versions of Atlassian platforms. However, they need control and more transparency into how much that shift will cost, said Jawharkar.

    At the same time, Atlassian views the cloud as an opportunity to expose more end users to its offerings by making them available for free. These editions of Jira Software, Confluence, Jira Service Desk and Jira Core will be available in the coming months alongside existing free editions of Trello, Bitbucket and Opsgenie.

    In addition, Atlassian is now extending its Cloud Premium service to now include Jira Software and Confluence, with a premium edition of the Jira Service Desk coming soon. Atlassian is also making 50% to 75% discounts available to eligible academic organizations and non-profit organizations.

    Atlassian is also moving to provide organizations with more control over where data gets stored. Customers now can choose where data in the Atlassian cloud will be stored to address regulatory compliance concerns. Atlassian also recently added a data encryption at rest and in-transit capability to ensure no data stored in its cloud is compromised by unauthorized access.

    In addition, Atlassian is updating Atlassian Access, a console for managing access to its various platforms, to include support for Google Cloud Identity and Microsoft Active Directory Federation Services (ADFS). Atlassian also committed to providing support for multiple cloud access brokers (CASBs) starting with an early access program involving McAfee and Bitglass before the end of this year.

    Atlassian is also promising enhancements to its audit log and early access to tools, which will help organizations better understand how Atlassian software is being consumed and their associated billing costs. The whole process of onboarding and offboarding users is becoming critical as organizations become more concerned about controlling their cloud application costs, noted Jawharkar.

    Finally, Atlassian is enabling customers to customize the URLs associated with Atlassian cloud service to reflect their own brands.

    Atlassian today has more than 150,000 customers consuming its software, including Costco, Delta Airlines, Office Depot and Visa. The most widely employed Atlassian application in DevOps environments is Jira, a project management application optimized for tracking software development projects. Atlassian is now trying to extend that base of customers to increase usage of OpsGenie, a set of tools for managing alerts.

    Obviously, each IT organization is going to transition to the cloud at its own pace. The issue most of them are wrestling with now is determining whether it makes more economic sense to move to the cloud or stick with the on-premises IT environment they already have in place.

    — Mike Vizard

  • Using Jira Software Search to Accelerate DevOps Workflows

    Using Jira Software Search to Accelerate DevOps Workflows

    Imagine driving down the highway and seeming to get a traffic jam at a distance. You realize your car is equipped with GPS to have clear visibility into what’s next and can show exact directions for alternative routes and estimated travel time. It is very easy to pick the fastest and most favorable route to reach your destination by looking ahead proactively and having the set of right tools for collecting information.

    The combination of Dev and Ops teams that are working together to build a faster and more reliable released pipeline is defined as DevOps. Similar to GPS, Jira Software acts as a singular source of truth for information development across your DevOps workflow.

    Complete traceability and visibility of work across different teams can get you surface information and data from an integrated toolchain to the right people anytime. No matter if you’re a team lead, release manager or a tester, the workflow visibility can ensure everyone by letting them know what’s in development and what’s being supported.

    In the latest release of Jira Software version 7.9, there is support added for the dev cycle to show development data from Bamboo, Bitbucket and GitHub in Jira Software search from your DevOps practice. It makes it a lot easier to identify development issues by making informed decisions and faster shipping with software development services.

    Get Answers to Development Questions via Basic Searches

    A new column called Development is added to the default view of Jira’s Issue Navigator in the latest release of Jira Software Server (v7.9). It allows viewing specified information pulled out from Bitbucket Server without clicking into the individual issue. Instead of limiting yourself to the single-issue information, you can see a high-level snapshot of issues coupled together by filtration, to help surface larger trends or problems.

    If this gets stopped at their source, does it really need to move the needle for improving your dev process within DevOps? For instance, if you wish to know how many issues under development, are they in the review?

    If you ever find that one or two developers are getting loaded down with the bulk of pull requests, you can immediately access if redistribution of work is required or not.

    Filter Out Your Development Information Using JQL

    What happens if you need to answer too many complex or open-ended questions? This can become monotonous after a time. You can use Jira Query Language (JQL) to create search queries that are based on development information to uncover key information for avoiding all pending problems.

    The latest version of Jira Software Server comes updated with the syntax to align the JQL query formatting. The users of Jira Software power use JQL for a long time to look at a subset of issues for driving reports and focus on Scrum and Kanban boards. With the help of cross-reference data from developer tools, Jira Query Language seems to be more powerful now.

    Examples of Jira Query Language in Action

    The teams who practice DevOps need critical internal and customer feedback, which helps them to inform features by making them higher quality and more valuable to the end user. Hence, focusing on feedback often creates tension when you decide if the first version is ready to deploy.

    You may ask: What number of issues are done but have not been deployed?

    From this question, you can determine whether the feature is ready to be released and starts collecting feedback or is blocking any issues that need to get resolved prior to release.

    Often, the team’s test builds locally before jumping off to deployment. If the same is the case for your team, then it is a good practice to regularly check the status of the builds.

    You may ask: What number of issues are failing builds?

    If you figure out a lot of failing builds, it may be a signal that the developer environments do not match the deployment. Generally, this is a problem you want to catch and fix right away, so conversely, the set of issues can be the areas where the testers can check acceptance criteria and begin exploratory testing.

    Boost Up Your Search

    You need to surface the information when and where it is needed as most of the teams get the most out of DevOps by bringing development, QA, high-quality releases, more-informed decisions and happy customers. Keep learning!

    — Kibo Hutchinson