We are using Insight for asset management.
We have a list of instruments (each instrument is an object) and a list of regular service tasks (also an object).
A service task is a referenced attribute on the instrument.
Each instrument can have several service tasks and each service task can be attributed to several instruments.
The instrument also has a date field: Next service date.
For instance:
Both the bicycle and the tricycle get the service task Oil chain but they do not have the same Next service date.
With automation we go through an instrument list (objects) daily and check if there is a service date coming up. If so a Jira ticket is created to perform this service task for that specific instrument. When the ticket is closed a script updates the Next service date according to rules we have set.
What we would like to do is make the service task's list of steps a tasklist (we are currently using the add-on Simple tasklists in other Jira projects) in the newly created Jira issue. Then we will use postfunction scripts to only allow the issue to be closed if the tasks have all been completed. We use this postfunction in other projects and that works fine.
The problem is this: Is it possible to somehow create a tasklist in the service task object itself that translates to a Jira issue, perhaps with some markup?
I hope this is not to confusing, I tried to make it as clear as I could.
Hi Soley,
You should be able to do that (the task list) if you define it as a textarea attribute type. This will allow you to store task lists on the object service task itself.
A small example would be
The translation however on Jira will have to be scripted via groovy or something else. You might be able to use the same add-on as you are using Today and the values from the attribute. But as I have not used it myself I cannot say for sure.
Cheers!
Nader
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nader.
Thank you for your reply :)
We will probably end up scripting this as you suggested but as a workaround until we do, we used the markup {task} in the textarea field in the object and Jira read that correctly as a checkable task in the new issue created with the automation rule.
Thanks again :)
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.