Gökçe Gürsel {Appfire} Atlassian Partner

You can set up an escalation service (Job) that runs the JSM SLA function breached() or everBreached() and set the date field accordingly. It has the set custom field snippet. You might want to add a if check to set the empty cfs only.…

Do you have Automation or Script Runner?

Hi @Jeffery Stone , I think there is an issue with your SLA configuration. I suggest starting with a calendar if you didn't define any. Your post indicates that the SLA shouldn't be active over the weekends so a standard Monday - Friday calendar should work. After that, you can go over your SLA configuration. You should…

Hi @Sean Roberts , You can do this by adding a script in the create transition. You can use Script Runner to add a custom script as a post function and add a comment. Adaptavist Library has an example: https://library.adaptavist.com/entity/add-comment-to-an-issue-in-a-post-function I've done some teats and adding the…

There might be other apps that are doing this like Script Runner or a REST Service is called? You can check the MAnage Apps page to see whether there are other apps that are doing this transition. You can also check the history of an issue transitioned this way and the user who performed the transition. That might give you…

Hi @Naomi Schwaiger , Welcome to the community! How is this automated transition is handled? Most likely, there is an Automation rule running in the background. You can go to Project Settings>Automation to check there is a rule configured and the set duration. Cheers, Gökçe 

Hi @Rob B , You can easily do this using Time to SLA. You just need to define a notifier to fire an event when the SLA is breached. After this configuration, you can easily catch this event with Automation or Script Runner and define a rule or write a small script to set the date field. Please let me know if you have…

I believe you need to be a project administrator in the JSM project or Jira Administrator. You can check whether project admins can set the rules by going to Project>Settings>Automation> Click ... at the top right corner > Global Configuration. Another thing to note here is that the Automation User should have the…

Hi, Creating a new linked issue in a Software project is easy to achieve. You need to go to your JSM project >Settings > Automation and a rule like this: Don't forget to add the "Linked issues" field to create screen of the Software project. Does this meet your requirements? BR, G.

Hi @[deleted] Welcome to the community. To link a JSM ticket to a software project issue, just simply click "Link issue", select your link type, enter the issuekey for the software project issue and you are done. You can also create the linked issue there by clicking create linked issue. Please let me know if you have…

You can also use it to search last 7 days. This field is searchable and sortable. Check it out: You can just try the plugin for 30 days (you can extend this trial period up to 5 times) and if you like the features you can request a quote. Enhancer plugin for Jira has many more features, Time in Status custom fields, Time…

Hi @László Földesi , You can do this using Enhancer Plugin for Jira. All you need to do is to add First/Last Comment Date custom field in Enhancer and you can do searches using this field. Please let me know if you have further questions. Regards, Gökçe Please note that I'm one of the members of the Snapbytes team.

Hi @Rik , You can do this using Time to SLA. You can use SLA detailed report to extract SLA dates and durations (working (time elapsed) and remaining) and SLA dates (start,target and end dates) and export them to Excel by clicking the Export button. Please let me know if you have further questions. Cheers, Gökçe Please…

Hi @Rick Perks , You can use Time to SLA to show your customers SLA start, end, target dates, remaining, elapsed and pause durations in customer portal. So, if you want to show your customers real time SLA data, Time to SLA is the way to go. Please let me know if you have further questions. Regards, Gökçe Please note that…

Hi @Csiszer Csongor , You can achieve this easily using Time to SLA and its dynamic duration feature. Just define your SLAs as wish. One way to go is starting your SLAs with Jira Field: Created or with the first status of your workflow and ending your SLAs with Jira Filed: Resolved or with your "Resolved" statuses (Done,…

Well, I'm out of ideas. @Liam Green you have any other ideas?

The history tab is not present in the screenshots but no worries. Can you check the Script Runner app then? Maybe there is a script listener or scheduled job configured?

When you click on 'All Rules', there are no rules listed right? If this is the case then, I believe there are no Automations affecting those fields. How about other apps installed in your instance? Also, is it possible for you to share a screenshot of the affected issue?

Hi Neeta, It looks like this for Software projects: In Service Management projects, it's near SLAs section. Since you have mentioned that the WF is the same, I can't suggest checking the post functions. One other possibility is another app setting those fields. Could you check which apps are installed in your instance?

You can go to Project Settings>Automation to see your automation rules. Also, You can click on the History tab right above the Comment section of the issue view to check whether the Automation app does changes to your issue. 

Hi njain2@markem-imaje.com , You can check the issue history tab to see whether there is an Automation rule working in the back. If it does, you'll see issue changes made by the Automation by Jira. Cheers, Gökçe

Hi @[deleted] You can measure the time spent in a task or a story with Enhancer Plugin for Jira. Enhancer Plugin for Jira has Time between custom field that measures time spent between two statuses /events. You can configure it to measure time spent between Created and Resolved events which will how you the elapsed time…

Hi @Kaur Joakit , Time to SLA has this capability. Just configure your calendars and SLAs and navigate to Generate SLA data for existing issues menu. Enter your JQL to determine the scope of the regeneration and click Generate. Time to SLA will do the SLA calculations for the older tickets so that you won't miss a beat!…

Hi @Vinod Madhappan , Your query is correct. You don't need an additional tool for this. project in ("ABC") AND status not in (Closed, Cancelled) AND priority in (Blocker, Critical) AND updated <= -4h AND type not in ("Deployment Request", "Operational Request") ORDER BY updated DESC Cheers, Gökçe

Hi @Vinod Madhappan , Jira's built in capabilities are enough for this requirement. You don't need an add-on. You first query is correct. project in ("ABC") AND status not in (Closed, Cancelled) AND priority in (Blocker, Critical) AND updated <= -4h AND type not in ("Deployment Request", "Operational Request") ORDER BY…

Hi @codingouch , You can use Enhancer plugin for Jira to identify such issues. Enhancer Plugin for Jira has Time Between and Time in Status custom fields that measures the time spent between two statuses/events and time spent in specific status. Time in status field gives you the drill-down information based on assignee.…

Hi @Gal26 , You can try the Comment Enhancer app for this. All you need to do is to create the Last Comment custom field in your Jira. After creating comment custom fields, add these fields to the relevant screens. Then you'll see that these fields are populated automatically by Comment Enhancer. For historical data,…

Hi @Nithya Vineesh , You can try Time to SLA to circumvent this issue. It doesn't have a limit on how many SLAs you can define. It is easy to use and has novel features such as SLA reset, SLA target date custom field, and detailed reporting. You can generate reports with a large number of issues with our asynchronous…

Hi Nithya, Since this is a relevant issue for you, I'm going to answer even though this question is old. You can try Time to SLA to circumvent this issue. It doesn't have a limit on how many SLAs you can define. IT is easy to use and has novel features such as SLA reset, SLA target date custom field, and detailed…

Hi @Carlos Ramirez , Your use case can easily be addressed by Time to SLA. All you need to do is to add a JQL condition to your SLA configuration and your old SLA data will be unaffected by your change. Also, With Time to SLA, you can regenerate your old data as well. So you'll have your new SLA configuration in effect for…