Automated Jira & Confluence Health Checks: How to Boost your Operational Efficiency, Productivity and ScaleLooking for those leading indicators that highlight risk? Looking for quantitative ways to drive better application and process enablement? As you implement your plan to execute on your Agile initiatives, you must ensure your Atlassian systems and processes all have business alignment, traceability and are healthy enough to stand one their own. Join us to learn how you can audit, manage and implement an Atlassian application governance strategy that paves the way to optimize for better governance and operational efficiency.
Don’t let your tools become a liability to your business!
Using Power Scripts for Jira and our Software & Process Health Reports, we have combined together an advanced Jira administration scripting framework and a complimentary process & system audit report into a powerful Atlassian Solution that helps you highlight and address system configuration issues, hardware and data integrity errors, process inefficiencies and other common issues affecting your transformation and governance initiatives hiding inside your instance. Knock down the walls today!
TranscriptionMonte: Today we’re going to dive in Part 2 of Cprime’s Jira/Confluence automated health reports. Really the vision here, for those of you who joined us in part one, was all about how do you quantify the quality of what’s inside of your Atlassian instance and we’re bringing you Power Scripts. We’ve extended Power Scripts with a framework for health and reporting. And so today, we’ll do a brief recap for those of you who are brand new today and didn’t have a chance to see Part 1, our approach, who we are. We’ll talk a bit about what Power Scripts is, talk about benefits and use cases and then we’ll use the remaining time to really go deep with Tim Reiking, looking at and running and really kind of spending the rest of our time here with the actual Health Reports.
So a little bit about us and our product development approach. We do custom product development, so whether that be Atlassian plugin development for our customers and clients, or are extensible framework and our Atlassian marketplace coverage. We have our own framework of apps that are solution focused around governance, compliance, workflow automation, integration use cases, and this talk is largely going to be focused on just how we’re taking those ecosystem of products, blending software and services to bring you things like Health Reports. And so one final note, in addition to health reports, be on the lookout for more horizontal product to product integration talks where we bring our Power Scripts product using the simple issue language (SIL) to Insight Management, Tempo, a Jira Portfolio Structure, draw.io, Comala Workflows. So whether that be, you know, insight tracking or time tracking or release planning and forecasting or issue traceability, visual diagramming or document teams managing a document workflow in Confluence. We want you to know that our ecosystem helps kind of extend a lot of that. So for those of you who know our vision, we don’t want to be another vendor off the marketplace, we want you to think of us as your strategic software provider or a partner in all of this. And so our goal is to really help you streamline process and workflow, consolidate all those plugins and use case functionality and ultimately get to kind one streamline with our framework of apps vs kind of what is the next plugin and managing all those disconnected plugins at scale. And so for us, we’re seeing folks leverage our framework to establish governance and guardrails, cut back on all that technical debt that you have to manage and ultimately just consolidating all those kinds of point solutions.
So, but for our Jira system administrator, when you think about a toolbox that works for you and you need workflows, integrations, custom solutions, think of us. So a little bit about Power Scripts for those of you who don’t know what they are. What is our vision for Power Scripts? As you can see here by the screenshot, it’s essentially a view through a window in the administration side where you can script up, extend functionality in Jira and it’s all about fast solutions. So our simple issue language (SIL) is an abstracted language layer from Jira, allowing you to kind of use Jira as contextual language, so issue type in key just as you would write a JQL query similar to that. And I think most importantly it’s all about reducing implementation time. We’ve seen it reduce that to even 50 percent so just get started, use it. It just works.
And so for us, it’s not going to break on upgrades. We manage all of the maintenance with Atlassian. And so you can, with full confidence know that if there’s a script that you write using Power Scripts, it’s not going to break on any sort of major or minor upgrades. We sort of take care of all that technical, batteries included, items there. And then it’s portable and extensible. So as you think about server, cloud, federated instances, that’s how folks are leveraging Power Scripts to kind of bring all that information together, really zoom in and understand what’s happening. And then extending Jira, it’s simple to use. So you don’t need to be technical. You don’t need to know Groovy, the Jira SDK, or any sort of Atlassian plugin development knowledge. It would be as simple as writing a JQL.
Some popular use cases? It’s really application governance, customers are using us to do things like permissions and restrictions. So maybe you want read only issues or you want to lock down certain issues. Maybe you want to restrict issue creation to a certain subset of users, disable inline editing, maybe it’s filled manipulation, things like, you know, if an executive needs a certain report later on down the line, you want to make sure that you’re requiring that field capture or helping to kind of automate field values on issue screens and edit screens on behalf of the user and then showing and hiding certain things from the Jira UI side, being able to manipulate the Jira UI to do things like customer messages, conditional alerts and notifications, being able to use color based on some conditional queries. So then kind of highlight red, yellow, green based on kind of things that are attached to the Jira UI and then ultimately in the context of your role process automation.
So as you think about advanced JQLreporting, you can extend JQL. Think about all the complex queries you’ve tried to run. We give you the opportunity now to extend that or write your own and go deeper into the JQL issue search, and really get in and pull out all that information you’re looking for; things like auto prioritization, issue aggregation in sum up. Everybody has a prioritized backlog, but being able to kind of use a script to help automatically start rank ordering that; things like custom calculations, governance teams are starting to think about custom calculations for a requirement score. So maybe success could look potentially like: if it meets this weighted average of this criteria, that’s a good requirement. So interesting ways that people are kind of establishing application governance with Power Scripts and then ultimately, you know, all the critical risks, blockers, dependencies, being able to highlight that and pull it back and showing that in an email report or in a Confluence page.
So let’s get into it. Let’s get into health reports and we’ve had a lot of great excitement around this. We have a lot of customers and cisadmins running this and we’ve got a lot of buzz around this. We’re going to kind of get started with at least giving you an overview of who’s using this and who are sort of personas. First it’s really been the technical Jira admin or the CISadmin, right? This is a user who’s implementing Atlassian. They’re chartered with setting it up, configuring, maintaining it. We’re also seeing sort of somebody on the business side, somebody who’s charged with the application governance initiative. They may be on the business side; they own standardization, normalization of process and technology. And so these two really these two roles are coming together to really kind of take advantage of health reports and really kind of go deep and then make those tweaks and optimize the system.
And then finally, consultants and partners. So for all you freelance consultants out there, other consultant companies or even other Atlassian partners, taking advantage of our product and our IP to kind of go deep and really kind of help your customers. So what does health reports accomplish? At a high level with Power Scripts we give you the ability to leverage prepackaged and prebuilt scripts to execute against your Atlassian instance. And what it’s doing is it’s just querying, reading, retrieving all this conditional information about your agile process, your Atlassian system configuration, to kind of pull back and leverage that information in a more meaningful way. We’re able to kind of land that information now in Confluence. So with this complex integration, we’re helping you with creating a space, landing this information, versioning those reports, and monitoring it over time. The idea is to really start executing quick automated health assessments and just kind of baseline that progress on your way towards better application governance.
This extensible framework, as I mentioned, you know, is a framework of prebuilt scripts, but it is extensible. So when you think about Power Scripts, we’re giving you a kind of precanned stuff, but, but you can also extend and custom your own custom tailored reporting and health metrics. And so it’s configurable, right? So if you think about how we’re pulling back that information, how we’re putting those guardrails around it, now we have our own configurable thresholds that allow you to kind of define success for application governance. So things like, maybe you want to set a threshold for planning and maybe you want to make sure that your releases have greater than 80 percent predictability, or whatever it may be, those thresholds allow you to kind of draw those dynamics and add them to what you’re querying and pull it back. So from a health check perspective, you know, what are our objectives, what are we ultimately trying to do, how do we get to the why? And it’s really ultimately to get to that visibility. So it’s, you know, uncover context and insights about what’s happening with your process and technology and again, prebuilt scripts, but extended.
You can then, once you get that visibility, then you can start to optimize and zero in on certain things. Being able to optimize your process or system. Once you then understand where those problem areas are rising and so maybe that’s at a sprint level, at a release level, maybe it’s at, you know, too many plugins are running your environment, a lot of different ways you can leverage these scripts to really zoom in and then make it a part of your process. Ultimately, why are we doing this? It’s to quantify the outcome. So you know, we want to make sure we’re measuring and quantifying how good is this quality inside of your Atlassian system.
And so what did health reports uncover? And really you’ll see this in a second. Don’t want to steal too much of the thunder from Tim, but you know, what does this look like? What is the output? We’re really starting to kind of draw it down to kind of these bucket areas of health reports and it’s really good key ways of uncovering collaboration and communication gaps, planning challenges of tracking and reporting issues, and traceability issues, traceability shortcomings, and then ultimately where does that lead to just better process in that process enablement so that you can kind of zero in and iron out the problems and make those appropriate tweaks. So, you know, what is the goal today? As I pass it on to Tim, it’s really going to kind of be looking at what’s in your instance, how do you get started, how do you visit the Atlassian marketplace, download Power Scripts, run this in your environment, see what comes back and then use this as an asset. So, Tim, I’m going to hand it over to you for next steps.
Tim: Okay, thanks Monte. So kind of getting started here. There are two major topics that we’re going to be discussing today. One is starting to integrate with your confluence environment to look reports as a whole.
The other one is to add your own kind of reports to the mechanism. So we’ll be covering the Confluence part for starters. Just to kind of cover what we talked about in our last webinar, if you haven’t seen that, I highly recommend reviewing that. We really talked about installation, what the report was kind of demonstrating, what kind of information you can get out of the primary report. And the original idea for the report was it was email based, it would send out to whoever executed the report will get an email about the report that they could share with their team. We kind of realized that you wanted to kind of see these metrics and do the tracking over time without having to search through emails and you know, finding a way to share that information with your team quickly and they would know that new things are out there. So the next step that we took that was integrating with Confluence.
And just as a reminder, this is what you’re looking at right now is our Bitbucket repository where all of our scripts are stored and everything gives you the installation instructions. So we’ve added some new installation instructions for Confluence that I’ll be going over here in a bit, but really what I wanted to see, what kind of benefits you’re getting now with the Confluence integration. So as part of that, now, you can add this to a preexisting space that you have in your system. It’ll create a new parent page and that will house all the pages, all the reports underneath it. So right now I’m looking at the health reports summary page here, that has all my previous executions on it so I can see, the titles of my pages, get the dates when they were executed, what type of report it was, and the system title.
But the real thing that’s going to be the most important for looking at this is what the score of the report, the overall report wasn’t being able to track that over time. So we can see here, with the going back and forth with these different reports that I had some dip in performance here that I was able to correct. And get it back, at least back up to what it was at this execution here. So now we have the ability to kind of track those kinds of instances over time. So if we look at the report itself, you know, it’s the same kind of report that you’re getting inside of the email that your team was receiving, but now it’s in a Confluence space, and now you can go in, you can add comments to the page, you can share it out with people, you have a lot more power to kind of see what’s going on with this. And how the report all works is it’s all html based, using the html map, present the exact same html information that was in the email and putting it inside the Confluence page. So kind of looking at this is the same kind of report that we talked about last time and the kind of information. So we’re getting like system check and integrity check and agile health report of epic story health, kind of seeing what’s going on, where can I improve my information, where can I improve my project over time. So that’s really the integration with Confluence that we’re really looking for here, is just to be able to see it, to kind of use that kind of theory of Confluence that it’s a collaborative space, so now not only is this report something that can help your team kind of increase your progress and everything like that, but you can also collaborate on and get more people, get more eyes on this report as part of this.
So I kind of want to just go back into the installation. So we’ve added a new section in the read me file here that talks about confluence installation. So there’s a couple of parameters here that we’re really looking for when you go through the installation process: Do you want to use Confluence? We have the ability to turn that on and off. If you turn it off, the email that gets sent out as part of the report will always get sent out to the person that generated the report. Really the on off switch is really whether or not a backup of that report is saved to the server or not. So if you’re using Confluence, it puts everything inside of the confluence space, if you’re not, it saves that file to the server inside of the SIL’s program file like it did on the last execution prior to the Confluence integration.
Where is your confluence instance, so the url of confluence, the username and password to use for creating all the different pages in there. So not only does it create that parent page, but also creates the pages underneath it and uses the page properties macro to report all that stuff up to the page parent. So we’ll need somebody that has a right abilities inside of whatever space that you designate to be able to create that kind of functionality. The last parameter here is the confluence space, so it’s the key that you want to use of the confluence space. That can be found up here in the URL of your space here. So I’m using the test space, so that is where you can get that kind of information. Some prerequisites that you need to do to kind of install the confluence integration is you need to have a space available, so we don’t create the space for you.
That space needs to exist so we can make sure that everything’s there. We have the right permission so we can do some functionality there as part of the installation process, so the space already has to exist. It doesn’t have to be an empty space, it just has to be out there and with the understanding that we are going to create this file structure here with this health report summary and all the pages underneath it, but the space that we’re putting that in has to exist prior to executing. The HTML macro has to be enabled on the Confluence system that we’re using because all of our reports are HTML based. We use this macro to display all the information properly within the space. There’s directions here that go out to the Confluence space to talk about that particular macro, how to enable it and what it does, some other information that you might need as far as enabling that macro.
The last prerequisite here is we are using a CSS style page to kind of get the look and feel for how the report actually shows up inside of Confluence. So we have a CSS file that you have to install as a part of your space. The nice thing is that our style sheet is non intrusive so it shouldn’t change how the rest of the space looks. It should be very zeroed into this specific report. We’re making sure that we’re using our own kind of information inside of the CSS style sheet to only target our information. There’s directions here on how to install a CSS style sheet inside of a Confluence space and that does require space admin. So a space admin will have to be the one that actually goes out and puts that style sheet in there. And also opens it up to, if you want to make some alterations to the look and feel of it, you have that ability to kind of go into the style sheet and make minor tweaks as needed.
So that’s really kind of the integration in here with Confluence, you can go in as part of, to get this kind of Confluence functionality, really all you have to do is just pull down the installation file, fill out all the new sections, fill out everything that is needed for the install and reinstall it. It should pull down all the newest code and install it into your instance and start using it with Confluence.
So let’s talk about customizing the reports. So, you know, as part of our report right now, we have very canned reports. It’s very something that we can go into and say what information do you want about your epic story health, unestimated issues, epics without fixed versions, these kinds of different topics. Here is something that we baked into the product by itself and you might be saying you’re something you’re like, that’s great information, but that’s not really where my problems are lying. And usually, you know, and I’m not surprised to say that a lot of people are using JQL and dashboards to kind of see their own reports and share out different metrics. That’s really where you can say this is the information that I’m really interested in.
We can start importing that into health reports and customizing it to get information that you actually want to see as part of your report. So we can add additions to these particular requirements here. You can choose to maybe you don’t care about sprint health and things like that, so you can actually opt to disable particular reports and everything like that if that’s something you’re not interested in seeing. If you don’t really care about one of these things and you’re just saying it’s just clutter and noise and it’s causing my reports to fail, you can actually disable it. The thresholds, you can actually adjust what the threshold value is. So if you’re saying, hey, you know, aging issues greater than six months, we’re at 38 percent, I’m okay with that. You can actually increase the threshold and say, you know, let’s make it 40.
So if it’s below 40 percent, this’ll still pass. So you can make adjustments like that. But you can also add your own completely unique reports that you care about this information that you’re really looking to get back. And the way that we’ve kind of set everything up is through CSV files. So everything that is customizable is in a CSV file that’s inside of a manager inside of the health report, a window here, so you can see all of our different CSV files that you can configure and you know, make your own. Inside of the installation file, there’s a breakdown of what all the different CSV files do. It’s underneath the advanced installation section. And if you scroll down, you’ll see a section called CSV breakdown. And this will give you a description of what each one of the header columns inside of that CSV file, what it’s designed to do.
The configuration file that we have listed here is something that done as part of the installation process. That’s where it installs your JQL query that we’re using as part of the installation process. Some different queries that you can put it in there so you can add additional configurations in there that you wanted, you want to have. So maybe you want to have a secondary, a filter to run off of or something like that. You can add that to the configuration file and call it out by name, using the dollar sign nomenclature here. The other sections here are our agile checks, so that’s where you can add additional checks, add additional information on the metrics CSV file. That’s really what you’re comparing those checks against. So that saying, you know, if I can look back in my report here, I’m saying an estimated issues, that’s my check.
What am I comparing it? That’s my metric. And the actual metric that I’m looking at is the total issues that’s inside of my report. So whatever is associated to your main filter here for. So in this particular instance, you can see I’m in project and test demo, you know, show me, run my metric against my total number of issues for that particular report. And that’s what the metric is, that’s using it there. And that’s where you can do into the customization of adjusting thresholds and things like that. The sections csv file that’s really designed to give you a look and feel of the report. So he says, you know, we use different headers here inside a red, those are different sections, so you can add different sections to your report to kind of break it up, to give, given a little bit more value of how it’s actually being structured so you can see that as kind of laying it out.
So maybe the particular check you want to have doesn’t really fall into sprint health or epic story health. Maybe it’s something completely different. You can add a new section and add it there. So kind of getting back into the configuration here. So I have a configuration that I want to add as a part of my report. So if I go in here and I load up my agile checks, you can see there’s a bunch of different information in here, all CSV layout, I’m going to add a new check inside of my report. So this is my check is to find any kind of issues that don’t have a description. Descriptions are really important to developers and if they don’t have a description that could really hinder my information and trying to get moving forward with that.
So kind of the breakdown, what it looks like here. So I’m adding an ID to my new check. So this is the unique identifier for that. The name that actually shows up in the report. so I can say, you know, this is the no descriptions check, uh, what is my filter that I’m actually using. So I’m saying, hey, grab my main filter that I have for my entire project and then put on this additional parameter here for, and the description is empty on my check itself as a JQL check. I wanted to show up in the epic health section and I want to compare it against the total issues inside of my report.
This next section here is whether or not I want to enable it or disable it. So I’m going to leave it blank. So that leaves it enabled. And then finally, here is a description of the information that I actually want that tells me something about what this particular ticket check is doing. So I’m going to save this and I’m going to get down to my system health and run the report. So this is running on my reports and even with the Confluence integration here, you’re still getting the full html output. So if you need to get the html for whatever reason, you can still grab it directly from the console. If we go out to my summary now, I should get a new report here.
Check on my epic story health. And you can see my new description here. No description or um, I have 65 tickets in that bucket here. I’m actually above my threshold because I want to keep it lower than 10 percent. I’m actually at 44 percent, so I failed that particular test. And then if I want to get actual information about what those issues are, you can actually click on here and it takes you off to the JQL to actually see that information there and what tickets and what they look like and start fixing them. So decrease that number over time to start fixing the problems. So that was as easy as just adding a new check and it was just trying to decide what my JQL really wants to look like. And that’s a quick JQL chat. So the other thing that I kind of talked about is customizing the look and feel. So you’re saying like, hey, that’s great, but I want to maybe I want to put it inside of a new section. So I’m going to call my section, you know, custom health and this is my custom health section
So I’m going to take this key now here, this identifier, my custom health. Go back to my agile check here and replace epic health, which is the current section it’s in, and replace it with my custom health. Click save. And I’m going to rerun my report.
So now you can see even in the header, just by me adding that new section, I already added a new custom health section here. If I click down there, there’s my no descriptions health, custom score for that. So now it’s entered it’s own a section here. It actually gets its own individual scoring mechanism here. So you can see I have a score of zero because my test in that particular section all failed. So I have a score of zero for that particular section. So that’s the basic layout. I’m kind of getting into the more advanced sections here. So you’re not limited to just using JQL for reporting mechanisms. You can actually do entire SIL scripts. So you can say, hey, like this one above here, a lot of the different version, information here is really all the version reports are all SIL script, just because they’re really complex.
It wasn’t something that we could do with just straight up JQL. So it’s an actual SIL script you know, Power Scripts SIL script that is returning this information so you can go out and you can say, hey, here’s my SIL script that I’m providing and then I can provide pipe delimited parameters to send into my SIL script. It’s a SIL metric. So that’s the type that it is. I want to put it in my version section here, here’s, you know, the metrics that I’m using against it and just some additional information against the metric itself. So that is the big thing that you can get from that. The requirement for adding a SIL script, a metric or a SIL script check is that you must return a numeric value or something that could be maybe an array of values that can be quantified into saying how many is it? So it can actually be scored, so that’s the main requirement if you’re going to go to the sole direction that it has to be a quantifiable thing. It’s not something that’s just going to be dumping information, it’s going to say I want to actually run it against a metric to get this kind of percentages kinda thing. You can do the same thing for metrics. You can make SIL script metrics to also do that to send back and the only requirement there is that it has to return a value. So if you’re pulling down and you want to see how we’re actually setting up SIL scripts to do checks and metrics, that’s all inside of our installation files here so you can get the exact location of our SIL scripts and kind of look and see how we did the different applications here to kind of start building up. If you have a really complex metric that you want to get that a JQL just won’t provide. So that’s another avenue to go to as far as customizing the system as much as possible. ,
Monte: So Tim, you know what we’ve been really focusing in on is Power Scripts for Jira and looking into Jira. One thing I want to mention just from a backlog perspective is that we are working towards creating Confluence specific health reports in the future. So stay tuned for that. I know Tim’s going to tease a little bit more about what’s coming in the future, but things like macros and usages and the power of Confluence in a similar report.
Tim: Thank you. Yes, so that’s really the bulk of the customization stuff and the idea is to not be limited to what we provide you as far as the canned metrics and the canned checks and everything like that. We really wanted to make it so it’s a powerful tool for you to get in there and get real information out. So that’s where we kind of opened up this customization avenue that you can get in there, you can add different things that are very specific to your company. So that’s where we’re at with the customization thing. I think we’re going to open it up for questions. I think we have a couple in the queue.
Myriam: Thank you Tim. So one of the questions is, is this a free thing and how can I access it?
Tim: So the scripts itself, the packaging is free, the report mechanism, everything, the only requirement that we have is you have to have Power Scripts installed. If you’re just kind of saying, hey, I want to know more about what’s going on with this report, you can get a 30 day trial of Power Scripts to install in your installation. Take a look at our repository out here, go through the installation instructions and pull it down for free and use it as long as you have a Power Scripts license.
Myriam: Okay, great. Thank you. Tim. And we have a Alexis asking a question of can I extend this and build my own query to understand permissions?
Tim: So yeah, permission to is something, you know that I kind of talked about that. It’s something that’s more complex than just JQL. So that would be an instance where you could build your own custom scripts, kind of get that information, but I’m going to actually kind of table that question because there are a couple things that we’re going to show you and it’s coming up in the next version to show you for our next webinar. So take a look there and maybe that’ll help you answer some of those questions you have far as extending and where we’re kind of going with the project.
Myriam: Alright, we have another question from me. I hope I’m pronouncing that well. What level of admin rights are needed to make updates to the records? And can anyone with access to Confluence and Jira create or update reports?
Tim: So as far as creating new reports you do have to be an admin for Jira to get into the SIL manager to kind of get into this level to start adding the new information as far as running the reports, one of the things you can do is you can actually use our SIL runner gadget, which is a dashboard widget and put it on the dashboard of any team space that you’re using and open it up to anybody that has access to that dashboard to run that report so they can. Anybody can then kick off the reports. You can actually put restrictions on it with the gadget itself on. But to actually do the customization, you do need admin access to Jira to get into the SIL to make those updates.
I think we’re just going to talk about a little sneak preview of what’s coming up in our next webinar. I kind of want to give you some information about where we’re going, and where we’re going to take the reports. So kind of where we’re at right now is we were looking kind of version one of this report was just kind of a proof of concept, seeing what we could start doing with it, getting user feedback andstarting to implement some more of the canned reports. Version two was more along the lines of getting the installation process streamlined, getting the look and feel more consistent, adding in some additional integrations with Confluence and starting opening up the customization process. With version three where we’re going next is really looking at providing additional information that admins have been looking for when they’re landing in a new section.
For a new Jira instance. They really want to start getting information out of that system that says what kind of health is my actual system in. So if I look at my reports here, we’ve added a completely new section here called administration health and really what we’re going to be talking about next time is things like what user installed add ons are there, who are the Jira administrators, both system and just administrators are different statistics that we’re going to be using, what we have a completely new report here called unused elements. So I’m just gonna kind of scroll down through to this, this new report here so you can see kind of the information that we’re going to start providing here about what add ons we have installed, breakdowns as far as administrators, what groups are set up as administrators, what users are in those groups and what level of access do they have.
: Some Jira statistics here. So we have like how many attachments are in my system, how many comments, issue types, things like that. So we’re really expanding out there. And then probably the most useful section of the thing that I’m the most proud of is what’s not being used that I’ve set up. So it’s great to know how many things are out there, but are we actually using it? So are we using all of our issue types, are we using all of our groups? Is it’s being used in some capacity and not only are we telling you what the information, you know, what the percentage of values of not being used, but then we give you a detailed section of what is actually not being used. So we will really break this down, you know, next time in our next Webinar I just kind of wanted to give a sneak peek of what’s, what’s going going on with that and where we’re kind of headed here.
So we’re really trying to get back information that administrators have been scrambling to get, you know, for a long time is have a quick way to kind of get this information. And the other thing that we’re going to be kind of talking about next time is upgrades and how do you get this new functionality and going through the upgrade cycle. So you know, you’re already using health reports, you love it, but you’re like, hey, these new features are great, we’re going to be talking about what the upgrade process is. So stay tuned for the next webinar and we’ll be talking about that in more detail.
Myriam: Can we have another question that just came through from Steven? Thank you. Steven. Is there a significant difference between what was shown here versus what is available in the early access cloud version?
Tim: With cloud, there’s a lot of the different pieces here that required database access and stuff, the health reports as far as agile and kind of some system reports aren’t, shouldn’t be available inside of cloud. We’re really focusing right now on the server side and we’re hoping to port this fully on cloud. That shouldn’t stop you from trying to install it on cloud and let us know if you’re having any problems and what kind of problems you are seeing, you know, any kind of user feedback that we can get as quickly as possible. That would be great. Kind of mentioning that as well. You know, we do have a link out here on our read me page here that talks about opening up tickets, so if you are starting to get into health reports and things like that and you want to start using it and saying, hey, I found this or how do I do this? then please bring up tickets there. We have some links that links out to our documentation and we will constantly be updating that information, kind of giving you information out to you when it’s available, but for the most part, everything that we showed today, you should have access to. But like I said, we’re focusing really now on server and hoping to have full integration with cloud in the future.
Myriam: So Eric asked is script runner for Jira or Confluence.
Tim: So this is Power Scripts and right now we’re really focusing on the health report we’re really focusing on, on Jira itself and getting the information out of Jira like Monte mentioned earlier, we’re going to expand that out and kind of get the same kind of information from Confluence instance that’s kind of down in our backlog right now, but really where we’re focusing right now on the Jira side and trying to get that kind of information out to our users so they can make sure that their system is running at optimal conditions and continually having the ability to skip quantifiable results out to say, Hey, my system is healthy on a regular basis. Yeah. And then one plug, I’ll mention there, script runner is a competitive product. This is Power Scripts for Jira. We also have Power Scripts for confluence. So, um, you know, everything you’ve seen today is all through Power Scripts for Jira and Power Scripts for Confluence. So I’m just wanting to kind of tie out on that nuance.
Speaker 2: So our time together has come to an end and I want to thank Monte and Tim very much for a really good deeper dive into the automated Jira and Confluence health for your instances. Such analyses can really help you with productivity, efficiency, and scaling. I want to thank all of you for taking the time to join us today and we hope to see you very soon on one of our other webinars.