1 answer
1 accepted
Dude!
Got it! :)
Sorry for the late reply but I reaaally wanted to do it! As I told you is a good exercise! Without getting into details of how and why, here is the solution:
- First, create a custom Insight object field. In my case I named it CDI.
- Place the above field on the appropriate screens of your project
- Setup CDI field but its all up to how you have set up your objects really (in my case Computers was an object one level below Hardware object):
- In the above settings change the "Date" attribute to yours, as well as both IQLs
- Create the following rule
- Adjust the rule to your likings
Rule
Overview of the rule. Keep in mind that you have to change the TRIGGER, most like to a scheduled one, to check once per day.
Create a Variable
Inside this variable we will store the insight object's value
Compare Dates
First value:
{{jiraDate.match("((\d{2})\/(Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec)\/(\d{2}))$").toDate.plusDays(7)}}
Send email
Of course you can change the following to your likings!
Results
I needed a few hours to get this working due to the fact that Insight Date Attribute was not in fact a date.
Hope that this was what you were looking for! Let me know if that worked out for you.
Alex
- Go to cog (upper right on your jira screen) and click it
- Click on "Issues"
- Find on your left the selection "Custom Fields" and click it
- Click Create Custom Field
- Click "Advance" and find the Insight Object custom field. Click it and select ok
- Give your field a name
- On the next screen place your field in the appropriate screens of your project
- Click "Update"
- Search for your field again and from the three dots on the right of your field click on the selection "Context and default value"
- Edit Object
- Insert appropriate values
- Click Save
All the above is kind of standard procedure for creating a Custom Field. And this custom field has to be populated.. :/
I think I did something wrong,...
FYI:
Thats where the attribute is, in insight:
Thats how i created the insight object. The Automation Rule is in ITSM - Controlling & IT
that's what i entered in the create variable step.
The variable dosn't get filled, it stays emtpy so it cant get the object to campare and wont send any email,...
Do you see any error I made?
BR Andy
Two things to correct:
And on the rule, while comparing variable, the second field must be populated with {{wartungsende.wartungsvertag bis}}
My Insight-Object looks now like this:
I changed the variable to this:
the coparisson looks like this, nothing changed
also tried changing {{now}} and {{wartungsende.wartungsvertrag bis}} at creating and comparing the variable, same result, no effect. could it be, because theres a space in {{wartungsende.wartungsvertrag bis}} ?
I changed .....toDate.plusDays(7)}} to .....toDate.plusDays(10)}}
So the date with 27.08.2022 is in the range from today +10.
@Andreas Dellmour for the rule to run you have to place it inside a project.
Within this project you have to create at least an issue and then populate your wartungsende field (click and choose from the dropdown) with the specific object. You have to create X issues which all will have a separate value from the Laptop object. You have 45 laptop object and therefore you have to create 45 issues in your project. Every issue has have on the wartungsende a unique value.
After doing that you have to modify your rule a bit more like the following:
You can enable your rule and click run rule to test it If everything goes according to plan you may have a similar audit log:
In the above image take a closer look and see that ONLY for the kox-3 issue an email was sent! This is because I have place a value on my CDI field only on that issue. For all other issues (kox-1, kox 2 and kox 4) no email was sent.
A look on my issue @Andreas Dellmour :
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.