Comments
-
Hi Xin, In the "Transition parent issue" postfunction provide the transition ID of workflow of parent which is from the status of "completed" to "In progress"
-
You can do as suggested by Nic, or you can write a script in the post function of create transition which validates that the current issue is a sub-task of project X and if it's parent is in state "complteted" then to transition the parent to "in-progress"
-
Please make sure the issues in status "In review" is being returned by the issue filter.
-
Yes, so just add it in the body tag , based on the logic currently present
-
You need to format the HTML and add logic as per your requirements, an complete example is here - http://labs.bsb.com/2013/06/customizing-jira-email-notifications/
-
Not sure, what exactly you mean by "tagged" , but you can be the default assignee for any ticket which is created, if the ticket chooses a component whose component lead is your username.
-
Hello , Please first check the notification settings for the project to make sure you have notifications configured. Then check the atlassian-jira.log for any exceptions. Then do the following steps - https://confluence.atlassian.com/jirakb/diagnosing-mail-and-mail-handlers-issues-229180314.html I am sure you will find the…
-
Shradha, it's not about permissions but whether you have the field "Sprint" on the "Edit screen" of the issue. Each issue has screens associated with it, which you can see in the project admin section. And then on the "edit issue screen" for the issueType you have to make sure that the Sprint field is present only then you…
-
Hi @Eren Gokcek I am not convinced by your argument "I'm not interested in creating issues via email – looks too complicated." It's an easy way to create new issue, just send a mail to an email address thats it! It's simpler than logging in and finding your project etc.
-
I had the very same idea, but I can't find OR condition in the create transition validation section.
-
Hi Matheus, I mean while creating ticket either Field A or Field B should be filled.
-
https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts(search for fast track transition)
-
you need "script runner" plugin and from the plugin please use the feature "Fast track transition"
-
thats just so so hacky!
-
thanks for sharing more info about it, as my requirement involved writing a long validation statement consiting of a certain scenario involving multiple custom fields and I wanted to restrict it to a single line of code but since cfValues doesn't work well with IDs thus would need to extract the IDs before hand.
-
I actually hard-coded the ID using the cfValues['customfield_1234'] convention but that didn't work, i guess to make it work using the IDs is by using what you shared i.e. extracting the IDs using the customFieldManager
-
for other readers - Here "Release" is the select dropdown where as the "myfield", "mynewfield" are of type Text field thus if they are null groovy will interpret them as false.
-
Hi @Sana Safai - Yes, ofcourse it would have an impact on the sytax based on the type of my custom field but I currently not concerned with that rather I am looking for a way to get the custom field values based on their ID instead of names in a long condition statement, see my comment in response to Jamie answer's. thanks
-
Hi @Jamie Echlin [Adaptavist] - My full statement involves multiple fields -issue.issueTypeObject.name != 'XYZ' || (issue.issueTypeObject.name == 'ABC' && cfValues['Release'].getValue() == 'True' && cfValues['myField'] && cfValues["myNewField''] && cfValues['MyFieldtwo']?.value?.size() > 0)
-
Install the script runner plugin ,its free and awesome - https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner auto close subtasks - https://jamieechlin.atlassian.net/wiki/display/GRV/Post+Functions#PostFunctions-Autocloseallsub-tasks
-
"odd choice of platform." - is an Understatement ;)
-
Hi Pierre, Why aren't you upgrading your OS, your gonna run into lot of compatibility issues, as it's really really outdated.
-
I don't think that Jira 6.x is really compatible with jdk4.x
-
Hello @zakirov_em Default values for system fields isn't supported in JIRA, please see here - https://jira.atlassian.com/browse/JRA-4812 But this functionality can be achieved using plugins like Script Runner. Please see here…
-
Also, you can vote here as well - https://jira.atlassian.com/browse/JRA-31806
-
Hi Kashyap, You are reading the wrong article, it's about restoring a project from server to server or from cloud to server, but your case is from server to cloud. For that you need to read here - https://confluence.atlassian.com/cloudkb/project-import-from-jira-server-to-jira-cloud-691012062.html
-
Actually I was looking for a way to avoid custom code, as in a Large and complex jira instance, custom code sometimes add to maintenance woes of admins/developers
-
Hi Tanner, I don't think the target issue(issue to be cloned) is created in the post-function as the whole point of using the post function is to create the issue itself, and once the post-fcuntion executes only then the target issue is created.
-
JIRA misc custom fields plugin, if script runner isn't your deal then
-
In your project admin section, do you have the right permissions for th operation - Assign Issues Ability to assign issues to other people. There might be a group/ role which can do the above operation are you part of that group or role.