I have an automation set that will create a new maintenance ticket whenever a change request that meets criteria is approved.
The issue I am running into: The team who controls the Change Request process uses custom date fields "Change Start Date" and "Change Completion Date", while our operations team uses separate custom fields "Start Time" & "End Time" for their maintenance issue types.
Is it possible to use the value of the CR start and end time fields, to fill the value of the Maintenance Start and End time fields.
Below
{
"fields": {
"customfield_10068": {{triggerissue.fields.customfield_10022}},
"customfield_10069": {{triggerissue.fields.customfield_10023}}
}
}
"customfield_10022": "Change Start Date"
"customfield_10023": "Change Completion Date"
"customfield_10068": "Start Time"
"customfield_10069": "End Time"
Modifying the request / issue types to use the same field is not possible in this case, even though I'm sure that would resolve the issue.
Hi @Brian Stephenson ,
what does the output of the audit log look like? could you share a screenshot?
Furthermore:
Smart values are case sensitive and as far as I know the „issue“ in „triggerIssue“ needs a capital „i“.
could you please try the following:
"customfield_10068": {{triggerIssue.customfield_10022}}
Best
Stefan
@Stefan Salzl @Benjamin @Joseph Chung Yin
Thanks for the quick responses, the information you provided will certainly help with other projects I'm working on.
This particular issue was resolved with the following change:
{
"fields": {
"Start Time": "{{issue.fields.customfield_10022}}",
"End Time": "{{issue.fields.customfield_10023}}"
}
}
Seems I was overthinking the location of the source value I needed to transfer to my new issue.
I've just run a few tests and all is working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To supplement what @Benjamin stated, here are the screenshots to copy from issue actions for your reference -
Hope this give you some ideas.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Viasat Inc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI @Brian Stephenson ,
This is possible through scripting and automation to copy a field to another field. You can trigger upon update issue event.
Here's a similar post that describes similar to what you are trying to accomplish.
-Ben
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.