Comments
-
What are the issues that they are facing?
-
It's a bug, see JBHV-304
-
what version of jira and the plugin? Also out of interest, why did you not use any labels referencing the plugin?
-
In behaviours - docn: https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html
-
You could also take a look at https://scriptrunner.adaptavist.com/latest/jira/recipes/behaviours/restricting-priority-and-resolution.html
-
This should be a browser function imho, not a confluence/jira function. Both Chrome and Firefox can do this, presumably IE can also.
-
Have seen something very similar before. Can't remember the solution - but try using jQuery.ajax instead of getJSON, with "dataType:'json'"
-
Can you post here the full condition. The lines I pasted above should be on new lines.
-
Can you add this to the conditon: log.warn "Request type: " + cfValues.get("Request Type")? true See what it says in the logs and report back pls...
-
You're welcome...
-
Things get complicated around cascading selects. Here is the condition: cfValues.get("Request Type")?.getAllValues()*.value == ['Retail', 'Add prescriber']
-
OK, so you need the Simple Script Condition (not validator). The condition for checking a cascading select should be what I put above... see what happens in the condition tester. Try that script both with an issue with the correct value, and issue with the wrong value, and an issue with no value. It might be necessary to…
-
@Dieter - yeah, they're all chucked into the map for convenience. Only for conditions though IIRC. (and only in this plugin of course). @Molly - > has a lot more too it than what I'm trying to do (I think) what is it you're trying to do? I thought you wanted to validate a cascading select, but I'm sure there's more to it…
-
Not in that way... for that example it would be like def vals = cfValues["Request type"]?.allValues vals[0] == "Retail" && vals[1] == "Add" You can put as many lines in the condition as you want, it will expand as necessary. Gory details:…
-
Just replace OR with || There is a condition tester builtin admin script, which is useful for honing your conditions/validators. You can also do pattern matching, and more complex stuff than checking the length.
-
Thanks ;-) It all helps in my quest to get to 2nd place...
-
Also don't forget to mark my answer as correct if it works for you ;-) And you can mark my comments as helpful if you like.
-
It's a very specific request so I doubt there is anything built-in. It's easy to do though with minimal programming... eg install script runner, go to validators, add validator, -> script validators -> simple scripted validator. Then the condition in your case would be: cfValues["ZipCode"]?.length() == 5 Obviously,…
-
Not my plugin... happy to give a referral to the "competition" though ;-)
-
JQL tricks has an inactiveUsers() function, or you could add it relatively trivially as your own function using https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions. Update: As @MattS points out below (thanks Matt), ScriptRunner has an inactiveUsers()…
-
Not hugely sure, but I can see a couple of possibilities: * Set up a script listener for IssueUpdated events, and you check if the sprint field has just changed. In the listener you run the jql function "addedAfterSprintStart"... if the results contain the issue then you can fire the alert or whatever * Option 2, same as…
-
The former. And also it's not a plugin, but a full-fledged web app. I wish it could be done reliably as plugins but for our (highly specific) usage it could not. More than happy to answer specific questions about accessing the project key (which is var selectors = ["#pd-key", "#key-val"]) or anything else but I can't post…
-
Hrm. I was only try to give you some ideas. And you said you didn't know how to do it with confluence, I tried to explain how.
-
And besides, the more people who say "I see the need for a nav bar like in jira studio" the more likely Atlassian are to implement, which I'd much prefer over something homegrown.
-
I have done one that is pre-production atm... each app has a plugin that writes a div at the beginning of the body, gets the current project ID and posts to a grails app that actually sends the banner content. The logged in user details panel is then detached and moved in to the banner. Looks great. Using the grails app we…
-
I think you want to set the values of a cascading select? I think this is still not supported.
-
You need to hide transitions using a condition. If the condition is not true, eg all sub-Approval records not in state Approved, then the condition won't be shown.
-
Hrm... splits and joins are not well supported in jira, eg I believe the bulk issue editor will fail. Approvals are best handled with sub-tasks in my opinion, with the appropriate post-functions to create them, and conditions to prevent the parent being moved forward. Permissions and notifications are much easier to handle…
-
Well, mostly you go into the issue navigator from a project context, so the selectedProjectId is already available. In which case all the options could be narrowed down to that project. Anyway, there's nothing developers hate worse than being told HOW to fix a problem. They should just know the problem is there, and…
-
And the bigger the instance the more useless this is. Along with showing every possible custom field whether they're associated with the project or not. Delivering this could be considered a downpayment on the enterprise licensing!