Tuncay Senturk _Snapbytes_ Community Champion

Thanks for reminding, here are the steps defined below: * Go to Behaviours section of the Script Runner. * Add a new Behaviour (name something and click on Add) * Click on cog icon and map this behaviour to a project or issue type, anything you want accordingly. * Click on cog icon and Edit * Select Summary in Add Field…

Hi @Kalon Mitchell Welcome to the community. As far as I know it is not possible via API. On the other hand, you can do that deleting those records in the changehistory and changeitem database tables but that's always tricky and not recommended. I do not think it is a good idea to calculate that data from database, as it…

Hi @Connie Leuderalbert Sorry for my memory! Which post is that? :) 

Hahah, at least there is an answer now :) 

Hi @Jose Suanzes This might help a bit. Note that I haven't tested it. I coded it just to give you a hint. // import and get these managers accordingly FieldScreenManager fieldScreenManager; FieldScreenSchemeManager fieldScreenSchemeManager; IssueTypeScreenSchemeManager issueTypeScreenSchemeManager; ConstantsManager…

Hi @Amine Mekki I do not fond anything wrong in your code. Are those values in the quotes correct? For instance "section", this is the most tricky part, you should use the exact location which are described here: https://developer.atlassian.com/server/jira/platform/administration-ui-locations/

Hi @Gunti_Reddy Sorry for the late response. getCustomFieldObjectsByName returns a list of custom fields of which name is the parameter you provided. It is always the best way to fetch custom field by ID, as you did later. Anyway, as far as I understand you're storing the parent issue key in a custom field. You can get…

Hi @Gunti_Reddy I can't see the screenshot about the error. Have you forgotten to attach it? 

Hi @Thomas Purkarthofer It seems that the URL is generated incorrectly. Have you checked those links getting "Something went wrong" error page? The devil is in details, you need to dive further. Check the URL whether it is true or not. By simply copy/paste to a browser would give you an idea. Is it http/https ? Is the…

Hi @BPSI Admin First of all, I'd suggest investigating the possible problems in atlassian-jira.log file. On the other hand, as far as I understand from your post, Jira becomes available (up and running) but it takes too long, also the response time is really worse which seems like a memory or CPU problem. You can have a…

Hi @Don Schier There can be several reasons for this. But from the first look below if statement seems problematic: if (comment.getRoleLevel() == <value>) comment.getRoleLevel returns an instance of ProjectRole class, so you can't do such equality. Instead, you should be checking as below if (null != comment.getRoleLevel()…

Hi, I know it might be late but for some reason, I saw your question today. There is no such limitation on Jira. You can have unlimited issues but you might have some performance issues.

Hi @rahul.shinde You should not change custom field options directly from database tables. Prefer using REST API so that Jira can update the database as well as the indices.

Hi @Farida Musayeva You're right 1.000 is the default limit but it might be changed within the advanced settings. * Go to: Administration > System > Advanced Settings * Check the values for keys: jira.search.views.default.max and jira.search.views.max.limit Hope it helps Tuncay

Hi @Stanislav I'm not 100% sure but it might be because of the database collation option. It should be configured to support utf8 and case sensitivity. I hope it heps Tuncay

Hi @Ken O_Brien Have you checked the application logs? atlassian-jira.log file will lead you to this problem as the devil is in the details.

Hi @Thayne Munson @Charlie Misonne is right, it seems like an indexing issue. If the issues are not updated after the custom field (which you use in your search) creation, they would not be seen in the search results as they are not indexed. You have to reindex the project/Jira in order to get accurate results after…

Hi @Julian Yamid Torres Torre Have you checked this documentation about getting SLA details for an issue? I reckon you'll be using REST API to get that information.

Hi everyone, Welcome to the community!

Hi @Nag Your code seems like "if Due Date field has no value, then XYZ will be required" Did you try changing as below targetField.setRequired(false) if (sourcefield.getValue()){ targetField.setRequired(true) }

It seems that the code worked well. If the snippet is the custom field code, then returning null would clear the field's content. 

Hi @Drew Nedderman Have you tried return null instead of return?

Why do they think it is a risky way? It is not risky unless you put the post function in the right order. On the other hand, I do not know any other way of getting the new value of an issue field which is changed via the transition screen during the transition. Since the change was not persisted, you can't get the value…

Hi @Ricardo Gonzalez I'm afraid you can't do that without an app.

Yeah, import in the second line was mistyped. It should be import, corrected.

Try this one below; import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.MutableIssue def mutableIssue = transientVars["issue"]<br>def customFieldManager = ComponentAccessor.getCustomFieldManager() def groupManager = ComponentAccessor.getGroupManager() def singleGroupCf =…

For those values you need to use transientVars["issue"] instead of using issue as below def mutableIssue = transientVars["issue"] mutableIssue.getCustomfieldValue()

Below is the unresolved issues watched by current user resolution is EMPTY and watcher = currentUser() and below is the issues in Open status watched by current user status = OPEN and watcher = currentUser() 

Perfect! I'm glad to hear that it helped.

I also updated the final code above. Thanks