Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

[Article] 4 new feature for DevOps in Jira provide more visibility and better insights


Jimi Wikman
 Share

Recommended Posts

  • Owner

One of the biggest cause for complicated workflows and custom fields is the fact that Jira has never been a deployment tool, but the teams need the visibility of deploys. With this latest update to Jira Software Cloud we see improvements in this field with no less than four new features. DevOps teams or not, this will make life easier for everyone.

While there are several add-ons for Jira Software Cloud that will tie together repositories with Jira, this is now a standard feature in Jira. That means that it can be used with no additional cost (except for the Premium features if you don't have Premium of course), which lowers the entry point substantially. Hopefully this will mean the end of operations based statuses in the workflow and custom fields to hold release data.

Code in Jira

Quote

Stay focused on your code and (almost) never be disrupted by another ping asking which team is working on what code and in which repo. With Code in Jira, anyone on the team can simply open this view to see the most recently active repos across Bitbucket, GitHub, GitLab, or Git Integration for Jira, automatically surfaced right in Jira.

This feature allows you to connect your repo to Jira so you can visually see the repos in a new tab in your project called Code. Doing so if fairly easy, especially if you use Bitbucket, but adding Github for example takes only a few minutes. The biggest benefit of this feature for me however is that you will see the repo information in the Jira issue itself. This provide a lot of information to the viewer on where this issue has been committed.

Screenshot 2020-12-06 at 14.25.48.png

 

Deployments in Jira

Quote

Anyone on the team can get a real-time view of where a deployment is, across any CI/CD provider, as it moves through the pipeline – without having to ask a developer. Since every work item across Atlassian and third-party tools is linked to a Jira issue, you’ll be able to track and measure from idea through to production.

This is where things get interesting.  With Code in Jira above you can see where your code packages are and their status. With Deployments, you can see where those packages also have been delivered to. This provides a very nice overview of where your code currently is available, which is what most people want to know when they try to build this into their workflows or work views.

 

Premium Features

The last two features are only available for the Premium version of Jira Software Cloud. Normally I don't like to have features split between a standard and a more expensive version, but these two features are all about measuring which I think is fine to have as a bonus if you need the more expensive version.

Deployment Frequency

Deployment Frequency (Premium).png

Quote

We’ve taken the metric that high-performing software teams care about most and expanded it to track performance across any CI/CD provider. Jira automatically calculates how often your team is shipping value and how this is trending over time so that you don’t have to manually coordinate across tools or bug your ops team.

 

Cycle Time

Cycle Time (Premium).png

Quote

Go beyond just measuring average lead time. Jira is the only tool that can track down to the granular view of each segment of the development workflow, since each piece of work across all Atlassian and third-party tools are tied to a Jira issue. Surface specific actionable insights on bottlenecks and optimize the team’s workflow as you go.

 

My Thoughts

This is a very good addition to Jira Software Cloud that have been needed for a long time. While I think the Premium features is mostly for numbers people and not really for the daily work I think this still is a solid addition. I would like to see the deployment information on the issues and it needs a connection with Insight, so I can connect deploys to my assets.

There is a lot of potential here and I look forward to seeing this taking further in the future.


View full blog article

Link to comment
Share on other sites

  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Similar Content

    • By Jimi Wikman
      The word continuous has become ubiquitous in the realm of Agile development and quality assurance. Continuous delivery, continuous integration, continuous testing, continuous deployment, continuous improvement – what do these terms really mean?
      If you look at an Agile life cycle that includes steps to plan, prepare, explore, realize, test, deploy and run, continuous integration comes early on, aligned with developers. With all the pockets of new development happening in Agile environments, there’s a lot of changes being made to the code, creating a heightened need for version control. Continuous integration was born out of a need to have a central place to save and store that code change, such as GitHub, and compile that code outside of their machines in the continuous integration server. This process creates the opportunity to match all the other dependencies and things that other people are building. And that's where unit tests live. Continuous integration includes things like ADO, Jenkins, freestyle and pipeline builds. 
    • By Jimi Wikman
      We are happy to announce that cPanel, L.L.C. has released an update for EasyApache 4! Take a look at some highlights below, and then join us on the cPanel Community Forums, Discord, or Reddit to talk about this update and much more. If you have additional questions, feel free to reach out on one of our social channels.
    • By Jimi Wikman
      PhpStorm 2021.2.1 is the first minor update to the recently released 2021.2 version. You can update through the Toolbox App, using the IDE itself, or by downloading the updated build from our website.
    • By Jimi Wikman
      Atlassian and Mindville announced on thursday that Atlassian has acquired Mindville.  This means that Atlassian acquire Mindville's asset and configuration management product Insight, which strengthen their psoition against competitors like ServiceNow.
      The CEO of Mindville Tommy Nordahl is well known to us in Stockholm who have participated in the Atlassian Usergroup events that I ran for two years. For many he is Riada, the company he started many years ago as the Atlassian company number one in Stockholm (and sweden?). Lately he has focused more on the asset and configuration managament product Insight and I am not surprised that Atlassian now have aquired it.
      Atlassian and ServiceNow are both gearing up for a battle. Since ServiceNow are strong in the asset and configuration management it makes sense that Atlassian want to stregthen their portfolio in their area.  With more than 1700 customers already and Atlassian now adding resources I think we will see the cloud adaptation speed up a lot.
      If you have not looked at Insight before, then I suggest you do. Not only is it looking great and is easy to work with, it is also powerful and a very useful addition to your support organization. Using Insight alongside Jira Service Desk and Confluence is probably the most powerful way to manage incidents in your organization. The fact that you can directly connect it to your development and opertions team who already work in Jira make it even more powerful.
       
       
      I just want to say congratulation to Tommy and his amazing team for this accomplishment. To Atlassian I can only say good job on this acquisition. It will take you another step closer to being the natural choice for mid sized and large organizations, just as you already are the natural choice for small companies and all development teams today.
    • By Jimi Wikman
      Atlassian and Mindville announced on thursday that Atlassian has acquired Mindville.  This means that Atlassian acquire Mindville's asset and configuration management product Insight, which strengthen their psoition against competitors like ServiceNow.
      The CEO of Mindville Tommy Nordahl is well known to us in Stockholm who have participated in the Atlassian Usergroup events that I ran for two years. For many he is Riada, the company he started many years ago as the Atlassian company number one in Stockholm (and sweden?). Lately he has focused more on the asset and configuration managament product Insight and I am not surprised that Atlassian now have aquired it.
      Atlassian and ServiceNow are both gearing up for a battle. Since ServiceNow are strong in the asset and configuration management it makes sense that Atlassian want to stregthen their portfolio in their area.  With more than 1700 customers already and Atlassian now adding resources I think we will see the cloud adaptation speed up a lot.
      If you have not looked at Insight before, then I suggest you do. Not only is it looking great and is easy to work with, it is also powerful and a very useful addition to your support organization. Using Insight alongside Jira Service Desk and Confluence is probably the most powerful way to manage incidents in your organization. The fact that you can directly connect it to your development and opertions team who already work in Jira make it even more powerful.
       
       
      I just want to say congratulation to Tommy and his amazing team for this accomplishment. To Atlassian I can only say good job on this acquisition. It will take you another step closer to being the natural choice for mid sized and large organizations, just as you already are the natural choice for small companies and all development teams today.

      View full blog article

×
×
  • Create New...