Comments
-
Do you mean unauthorized users can inject ? I am not aware of that.
-
Which is your request exactly? Want to know if this is possible?
-
This is not a field you can "set" / update. It's a dynamic field which displays a calculated value based on the issue's "variables". Function wise. You cannot "hard set/code" this value.
-
Try just adding "@@Formula:"
-
Hi, If this was a "regular" custom field update is possible. This however I assume must be a syntax mistake, because this is a dynamic value, not a stored one. This is my formula for a sample field: Total Estimation <!-- @@Formula: (issue.get("customfield_10506") != null ? issue.get("customfield_10506") : 0) +…
-
Edited: Is that caclulated custom fields addon?
-
Configure a Permission Scheme based on Project Roles, where Assignable User permission is set for example to role "Developers". And for each project, add the required developers in "Developer" project role.
-
That is it's purpose. However in your case you do a simple JQL filter assignee=currentUser() and resolution IN (desired resolutions here) or assignee=currentUser() and resolution NOT IN (undesired resolutions here) Then, add a Filter Results gadget in System Dashboard (I'm assuming that's what you have setup) to display…
-
Use the database. You can either connect directly to it, or use a SQL addon. If am not mistaken something like "SQL Driver for JIRA"
-
Seems like no screen is configured. Weird
-
Could you post details of the transition ? Maybe a bad post function or screen selected?
-
What you are asking for, is essentially a listener function. So if issues match a certain criteria, let's say STATUS=REVIEW and updated <=startOfDay(-3) --unfortunately no business days as far as I know of, if condition is met trigger a transition. This would have to be run periodically, let's say once a day. Though no way…
-
I'm confused. You can directly export the issues and have the custom field values embedded (as direct values only, not reference). Though, if you wish, you can of course directly query in the database. You only need to check 3 tables.
-
To run advanced JQL, some kind of addon is required. You could easily do it by JQL but I don't think there are functions built in for searching linked issues or parent issue. I apparently keep saying this everywhere lol, but try ScriptRunner
-
This is definitely possible. Though circumstances are different. Applying any kind of logic, requires a scripting add-on. I recommend ScriptRunner by Adaptvist
-
Depends on what you have. Any scripting addon installed?
-
issue.getIssueTyoeObject() is supposed to run for an issue object, not a field one. def issue = getFieldByName("Data Enhancement") This doesn't make any sense.
-
So easily you could just set up a Confluence Group then and assign that group view permission only in each space you require.
-
I get it, people don't always like change :P. What you are describing really is the oldest approach, compared to pull at least. Anyway you have to understand that people, at least here, will always "fight" you for this old approach, even though it seems it's not up to you lol. You could run a small demo though. Why not…
-
Hi Tao, ScriptRunner, as Nic says is certainly the way to go. Though, with some creative thinking you could get around this. 1-There is a free add-on watcher custom field, which syncs with the watchers field, this way you could update it using a simple post function. 2-There is a component watcher free add-on, same as…
-
Perfect
-
Can you post the whole script? Also, you could just verify by getting a list of available actions .getName() to see the transitions available at the current time.
-
Anytime
-
You need some type of calculated field where you can write logic. Sorry, I can't think of any other "good" ways of achieving this.
-
Sorry can I ask which is the benefit of this? You could just add everybody as a watcher/participant and easily do the filtering on that.
-
Generally speaking, having a "robot" user for these kind of stuff is better. First, even though I'm sure this works, try a different action instead of transition. After you verify that, check the issue and try to transition manually. Judging by the error thrown it looks like some kind of validation error.
-
I've heard about scripted fields implementations for SLA. This might be an example, but I'm sure you can find others https://mraddon.blog/2016/06/09/calculate-the-sla-with-scripted-field-in-scriptrunner-for-jira/
-
You need to check the workflow. Try "debugging it" , log in to that user and try to transition the issue manually. Seeing your screenshots it should work as you are specifying, meaning transition main issue.
-
Is the user which runs this rule, granted Transition permission for the linked/main issue project?
-
See below comment from Alexey. Missunderstood the question. You need to configure behaviors.