Comments
-
Can you please tell me your use-case? Why do you need to query directly DB when JQL provides the same functionality.
-
Hello Board is nothing more than a view on a set of issues. Issues on the boards are fetched from a JQL filter itself. Thus, if you go into the board configuration and see the saved filer then you can see the list of issues appearing of the Board. If it's a scrum board and you are only interested in issues an an Sprint.…
-
You can add a post-function to set "Resolution" and that should do the work. From the docs about workflow triggers How triggers relate to other workflow operations/constraints When a transition is triggered automatically, it ignores any conditions, validators or permissions configured on the transition. However, post…
-
Have you looked into 2 dimensional gadget provided by JIRA https://confluence.atlassian.com/jira064/adding-the-two-dimensional-filter-statistics-gadget-720416991.html You can map component vs issueTypes in above gadget.
-
To update the issue in "Listener" you have to use the "issueManager" please see code snippet here https://community.atlassian.com/t5/Jira-questions/Custom-update-listener-to-set-subtask-s-fix-version/qaq-p/591808 basically add in the end and that should do the trick issueManager.updateIssue(event.getUser(), issue ,…
-
Using script runner plugin, the script will be part of "validate" phase of the "create" transition thus, validation will execute after pressing the "create" button. If you want a client side solution (though JS solutions arent always the cleanest) you can look into "behaviour module" of the scriptrunner plugin…
-
Hello Michael, Your requirement is a bit tricky to implement in JIRA without plugins. Because in JIRA, you have event called "issue updated" (not status but any updates on issue) Now, you can create a custom event and fire that event in the post-function of every transition. That custom event will be listed in the…
-
But where do you want to use it? In the *post-function* of create transition or in the *Listener* ??
-
Hello Marcus, This code should work fine in the "post-function" of the create transition. Where are you using the code?
-
Here I take into account that the issue has only one fixVersion associated with it or the first one is taken into consideration if there are many values for fixVersion on an issue. Also TimeStamp is of type java.sql and Date(releaseDate) is of type java.Util .
-
Once you have the issue object you can try something like this def version = (Version)issue.getFixVersions().first() if(version) { def releaseDate = version.getReleaseDate() if(releaseDate) { issue.setDueDate(new java.sql.Timestamp(releaseDate.getTime())) } } API reference…
-
Also possible via some JS hacks to hide the "create sub-task" button, though I avoid writing JS.
-
Pretty old question Not supported out of box - https://jira.atlassian.com/browse/JRASERVER-7990 Using script runner plugin you can put an condition in the "validation" phase of the create transition…
-
Without the plugin, the only way to do it is to use simple Javascript which you have already shared in the question. But this is not supported by Atlassian. The JS code which you have written, doesn't take into account the "change"/ "blur" events i.e. when do you want the field's value to be filled. So you have to write an…
-
First, please check if you have "script runner" plugin installed, if not then the approach I suggested to you isn't possible as it requires an plugin.
-
https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/servicedesk-workflow-examples.html
-
It's pretty much wrong at many levels, you are inserting JS in the post-function which is not required, try to put the script as i have mentioned in the previous comment in the "Script post-function" and then custom script post-funciton
-
Can you share screenshot as to where you are adding the script. You have to add the script in the post-function of "Script Post-Function" and then "Custom script post-function"
-
It's not supported by Vanilla JIRA. But can easily be achieved using Script runner plugin. Basically in the script listener, you can listen for event "VersionCreated" thus, for version created for a specific project you can execute an REST call to create an confluence page. Please see complete example here…
-
It will happen after submitting the request, but the field can be hidden on create screen and populated in the post-function so that it's visible on the view screen
-
You can in the "post-function" calculate the different in dates of two fields and then populate the required custom field in the post-function transition, thus it will save you from writing JS as things happen in the postfunction.
-
Types of permissions There are three types of permissions in JIRA applications, and they range from the high-level to granular: * Global permissions - These apply to applications as a whole, not individual projects (for example, whether users can see the other users in the application). * Project permissions - Organized…
-
Hello Chris, For your requirement, you would have to use the concept of "Issue level security" In JIRA the permission scheme is based on all issues of the project irrespective of issueType. Since in your case you want restrictions on certain Epics, thus you would have to implement issue level security on the epics. please…
-
yes, you can do it i.e. Use an released version on a new/later ticket as the value in the fix version field. There is an open ticket in JIRA to not allow it. https://jira.atlassian.com/browse/JRASERVER-2236
-
Hello @Daniel Lipovac Using JQL you can *Search* for some fields's history using the WAS operator. But you can't extract an report of all the values the field had in the history. Though you can use script fields (script runner plugin) to display history of a field on the issue view screen or write a script in the script…
-
https://www.udemy.com/java-the-complete-java-developer-course/
-
I don't think this question is directly related to Atlassian community. But still I will suggest you to start of with reading "head first Java" or do a Beginner's course on "Udemy"
-
Hello @Rodolfo What version of JIRA are you using. As this is working for me i.e. I can add "Team" field in the "Issue Detail View" configuration section of the Board;'s configuration. And then when I click on a issue card then I see on the right hand side the detail view on the board and team field is present on the issue…
-
https://scriptrunner.adaptavist.com/latest/jira/fragments/WebResource.html
-
You can use "Script fragments" to install a web resource which is basically a javascript that will hide the intended fields. Though not among the most straightforward things to do as I feel there is lack of sample documentation for this kind of examples. May be contact someone from plugin support for samples.