Comments
-
I believe You are referring either to JIRA SW project or JIRA SD project: With JIRA SW I would start from checking working days: https://confluence.atlassian.com/jirasoftwareserver/configuring-working-days-938845342.html With JIRA SD - with SLA…
-
I would try Object TypeID parameter instead of name - don't know for what reason but with some IQL functions these work better. If still nothing - post a ticket to Riada Support - I love those Swedes for prompt replies and fast turnaround with requests (recently my team logged 8 within a month - all resolved within 72h)…
-
WIth just Insight and JSD - there would be problems with achieving these (although with second point You might look into Insight automations + some scripting). With 1st one - You refer to Insight "watch" or JIRA ""watch"? first option - You will get notification on object changes (if setup properly) second option - does…
-
Actually we do the the other way around: - Org structure (departments, cost centres, other organisational assets) stored in Insight for JIRA structures. - approvers auto populated into fields based on attributes in Insight objects (e.g. Manager, Owner, Approver)
-
It is rather for IQL (Insight Query Language) from Insight for JIRA. AT least as I look at the screen. :-)
-
Riada has got pretty nice documentation on Insight so I would start to look at https://documentation.riada.se/insight/latest/insight-advanced-usage-guide/insight-for-developers/groovy-scripting/groovy-script-examples Then - (consultant's answer) it depends on use case. :-)
-
The greatest advantage and disadvantage at the same time of all Atlassian products is their openness and flexibility. Therefore You need to think carefully what are the goals You want to achieve to not "overtake" the solution. In other words: KISS, JIRA ADMIN! which is... Keep it simple, stupid
