Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Okay so we have a request to have the due date field to be set by the Time to SLA plugin.
"I am trying to pull in and show the date when the SLA is set to expire on tickets - this value is seen in the ticket UI within the SLA module. I coul not find a field to pull in into my widget on a dashboard...
Pl see links below for example an let me know what field should I pull in...
This is NOT the "Due Date"..."
I have thought about using "Automation for Jira" to run a scriptrunner script to do that.
When I pull the script from https://confluence.snapbytes.com/display/TTS/Groovy+scripts+for+TTS+fields and edit to have the correct field ID it still shows an error "static type checking errors".
Am I trying to go about this the wrong way?
How can once I pull "expectedTargetDate" to get that into Due Date?
Hi @Gaven Ray
Did you have a chance to check this article.
To summarize, you can define SLA Dates custom field to extract any SLA date to a regular Jira custom field, then you can use that field in any of the report, gadget or integration API.
I hope I was clear.
Cheers
Tuncay Senturk
Hi again @Gaven Ray
As the product manager of Time to SLA app, I just wanted to know whether the article was helpful for your issue.
For further assistance, you can always raise a support ticket here.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So adjusting the settings as suggested and they now show up in the columns for search. If I could get it to edit the actual due date field it would be great. The automation does not see it as a date field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Gaven Ray
Actually they are date fields, they implement DateTime interface.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Automation plugin is not seeing it as a date field. @John McKiernan1 do you have any insight here or should I open a support ticket against your plugin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What should we do in order to be seen in Automation plugin.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Daniel,
John from Automation for Jira here.
I am not familiar with the 'Time to SLA' plugin.
However, from what you describe this should be possible to do.
Assuming there is an SLA time as a custom field somewhere, you would just need to use a rule like this:
It's a bit tricky to decipher from her so if this doesn't answer your question, please pop a message through to our support team so we can look into this plugin a little closer.
Thanks!
John
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.