Ivan Tovbin Expert

Hi, If this is a post function then your code should be as follows. I'm going to assume that ID of your custom field is 11111 and its type is 'text (single line)'. import com.atlassian.jira.component.ComponentAccessor def userManager = ComponentAccessor.getUserManager() def watcherManager =…

Hi, Assuming the ID of your 'vdi' field is 11111, the code for a scripted validator should be like this: import com.atlassian.jira.component.ComponentAccessor import com.opensymphony.workflow.InvalidInputException def vdi = ComponentAccessor.getCustomFieldManager().getCustomFieldObject((Long) 11111) if…

Well, you can use a groovy script to write those comments into a file, that's another option.

Hi Bhav, The only way that I have found to extract these comments is to get them directly from the database.

Hi David, Check out this documentation on how to clone issues.

Hi Steve, If you have Scriptrunner add-on, you can easily implement this using a scripted field. The script behind it will basically go through all subtasks of a story (if any), check the status of each of them and return the earliest one as the field's value.

Hi Scott, I might be able to help you out here. But first could you give me the list of all involved fields and their field types. Also I'd like to know, all these different issue types, how exacly are they related to each other (issue links or subtasks, etc).

Indeed, Mike is right. Currently a field is NOT displayed on issue view screen if it has no value set. There's an open feature request here, so feel free to vote and watch.

If the current user will add a comment BEFORE clicking on the transition button the the condition for a transition WITHOUT a screen will be met and it's button will appear. At the same time, the condition for a transition WITH a screen will no longer be met and so it's button will disappear. As for the scripts, here's the…

Perhaps there's a validator set on your 'Create' transition which requires you to fill in this field?

Scriptrunner allows you to write custom scripted conditions, which gives you a MASSIVE flexibility in choosing your options, so if you happen to have it, then it can easily solve your issue. If you need help with writing a script for your custom transition then do let me know, I might be able to assist.

Ah, I see. Thank you for the clarification. This is totally doable. What I would do, if I had a similar issue is I would created TWO transitions, one with a comment screen and one without. Then I would configure two conditions, one for each transition. One condition would show the transition WITHOUT a comment screen only…

Indeed, the list of conditions which is available out of the box is rather limited and does not really allow much flexibility. Fortunately however, many 3rd party plugins add many different validators, conditions and post functions. I would recommend JMWE for starters. It has a ton of built-in conditions and also allow…

Hi Tom, You don't need Scriptrunner for this. Simply add a screen to your transition. Check out this documentation for more info.

Hi Matthew, 'All' or 'Global' transitions can have the same conditions, validators and post functions like any other regular transition. So in your case you have set up a condition which would only allow this transition to be triggered if issue's resolution is set to 'Done'. More info on workflow transition conditions is…

This can be done by modifying the 'pcounter' field in the 'project' table in Jira DB. However this method only works for Jira Server and since you are on Cloud and as such don't have the access to your Jira DB, this won't work for you I'm afraid.

Hi Jack, We've had a similar issue. As you probably know if your project is set to only accept emails from customers in your customer list, and then an external customer tries to send an email, then Jira simply silently ignores such an email (which can be seen in your email processing log). What we did to remedy this is we…

Hi Oliver, Would you consider turning administration mode off for good?

Can't say for certain about cloud. Check out vendor documentation. And if that doesn't give you a difinitive answert you can always try it for free to find out, just like any other add-on.

I usually advise users to NEVER touch Jira DB. That said, if I had to do something like this, I'd create a new multi-line text field and then use a groovy script to copy the value from the old field to the new one in all required issues. After that's done, I'd simply delete the old field. The same approach can be used to…

@MAG-II I might be able to give you a hand with scripting if you'd like. Given your use case it's not really too complicated.

Hi John, This can be achieved by 3rd party addons like Scriptrunner or Power Scripts. You can use their Behaviours or Live Fields (respectively) functionality to set the issue type on the 'Create' screen dynamically based on another field's value.

You don't need scripting to do it. If your Jira version is 6.2 or later then user filtering for single select user pickers is part of standard funtionality. All you need to do is create a User-Picker (single choice) custom field and then set which groups it will be limited to in its configuration. More details in this…

Security levels are easy and it consists of two steps: 1) You first create a security level itseft. 2) Configure who has access to that security level. Please check this documentation for more details. After you have your security levels set up, all you need to do is add a post function to your 'Create' transition (make…

Check the searcher for this field and make sure it is set to 'User Picker & Group Searcher'. Go to Administration -> Issues -> Custom Fields, find your field, click on the "Cog" icon to the right and select 'Edit' in the popped up menu. However if I understood what you are trying to achieve correcly, then It won't work.…

Hi Michael, If I had to do something like this, I'd definately go with Issue security levels. You can configure each security level to only be available to certain users/user groups/project roles/users or groups in a custom field. That said there's a couple of options here: 1. Use a workflow post function to set a proper…

Hi Ben, It should be: issue.getEstimate() and NOT: Issue.getEstimate() The same goes for: issue.getOriginalEstimate() and issue.getTimeSpent()

Hi Katherine, If you have add-ons like Scriptrunner or JMWE you can write a scripted validator, which will do exactly what you've described.

Cheers for update @Alexandra Steinberg. Frankly I wasn't aware that it would actually work. Good to know. Incidentally, I think the reason why your original code didn't work is because you treated your 'lob' field as a free text field and not a select list. Thing is, getCustomFieldValue() method returns different object…

If we are talking about 'Create' transition if you would place this post function first in the list of post functions then it simply wont work, because the issue won't exist yet when the post function would be triggered. An issue is created via a system post function "Creates the issue originally" which you can see in the…