Tuncay Senturk _Snapbytes_ Community Champion

Hi Amber, JIRA Enhancer Plugin has Assign to a User in a Role and Assign to a user in a role, based on a field of issue post function workflow postfunctions. You can check and watch screencast on site www.jiraenhancerplugin.comand documentation page. However, at the moment it is not available for "on demand" instances.…

Hi Rafael, At the moment, you need to repeat non-working days every year, but we have plans to implement the feature. If you raise an issue here, you will be able to get notified about the process. Regards Tuncay

Hi, Sorry for the delay, I have just noticed your question. Somehow I could not get a notification. JIRA 5 is not supported, you at least need to have JIRA 6.x Sorry again for the late response Tuncay Senturk

Hi Karan, We are implementing new gadgets to display SLA results, and we may implement your gadget request. If you clarify the request (screenshot or wire-frame would be appreciated) and raise a ticket here, we will try to implement it ASAP. Regards Tuncay Senturk

Hi Kate, - go to your workflow step and click to transition (for instance Start Progress) - Click Edit button - You should see "Transition view". - Change it from "No view for transition" to any screen - Publish workflow That's it. Tuncay Senturk

Hi, I do not know much about script runner but JIRA Enhancer Plugin comes with this feature. http://jiraenhancerplugin.com/documentation.html#assign-to-role-based-on-property-function Tuncay

Thanks Reza, definitely what I was looking for.

Hi Daniel, Sorry for the too late response, but I recently ran into the similar problem, and I found your question. When I looked at Lucene API and after some googling I found this issue. JQL has a limit of 1024 clauses, you can only get the expected results for <1024 rows. So, if you have more than 1024 fixVersions you…

Hi Simon, There's a new SLA Report where you can filter or sort all SLA data. Please check our documentation about SLA Report. You'll like it.

Hi Simon, Time to SLA field is visible if there is a valid SLA for that issue. I mean if you defined an SLA Open to Resolved, and your issue reached to Resolved state, the field is not seen anymore. Tuncay

I am not 100% sure, but I suppose component-import in atlassian-plugin.xml would solve the problem.

Hi again, The problem fixed with the latest versions (5.20.1 for JIRA 6.x, and 6.15.1 for JIRA 7.x) Regards Tuncay

Great, thanks

Hi Jasper, Thanks for the feedback. This is a bug introduced with latest version. We'll soon fix the problem. Could you please raise a ticket here so that you'll get notified about the progress? Thanks

Hi again, Since the issue has been created anonymously, notifications will not be sent to you automatically. Could you please watch the issue and discuss the details there? Thanks Tuncay Senturk

Hi Ty, The issue is under development. I am going deeper on how to speed up the report. OTOH it is getting time. Thanks for your understanding Tuncay

Hi Ty, I will have a performance update on History Report, however could you please raise an issue on this subject, so that I can understand the exact problem. And please provide more info about the issues that will be the result of the report. - Around how many issues are being expected? - Can you get report if you filter…

Hi, Enhancer Plugin has a post function, just as you want * Assign issue to user in custom field post function: Post function to assign issue automatically to a user that is set within a User custom field http://jiraenhancerplugin.com/#/documentation

Means your Joda time version is not up-to-date. Anyway try below instead if (slaDateValue.toDate().after(now.toDate())) { return 0} also add this import import org.joda.time.Days;

As Kristian mentioned, this script works against issue's due date field. If you have a custom field that works just like your script, then my script above will work just as you expected. have you tried that?

I did not test but it can be similar as below, hope it helps Bear in mind that it returns as days (24h = 1d), and does not count against working day/hour, nonworking day, .. I strongly recommend using Time to SLA import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.issue.CustomFieldManagerimport…

Hi DF, I could not see any question in your comment, however have you seen Time to SLA Plugin You can easily define SLAs and see countdown, see overdue, get report, and etc Regards Tuncay

Or you need to write your own plugin with a workflow post function. In the post function you can get custom field values and change the assignee of the user as Rambanam said. Hi again, JIRA Enhancer Plugin has a post function "Assign issue to a role based on a field in issue" You can do such assignment using this plugin…

Hi Ganga, Could you please raise an issue to our tracking tool?I will also fix those broken titles comes with JIRA Gadgets Plugin.

I double checked with fresh JIRA 6.4.11 installation, and I could not reproduce the problem. It seems that your JIRA could not replace internationalisation words. Anyway, is it working this way? Of course I will deep dive and fix the problem but, I want to know whether it is just i18n problem, or the functionalities do not…

Hmm, I see. Please give me time to reproduce the issue.Tuncay

Hi Those problematic fields comes with "Atlassian JIRA - Plugins - Gadgets Plugin" which is a built-in plugin. I am not sure why you do not have this plugin. Could you please make sure that this plugin is installed and enabled? Under "JIRA > Admin > Add ons > Manage Add ons" select "System" rather than "User Installed"…

Hello Jimy, Sorry for the late response. Could you please raise an issue here with following details? * First please try with longer SLA durations, for instance 4h SLA and 3h 55m for notify before. * Attach definition screenshots of both SLA and notifier * Attach related logs Regards Tuncay

If you specify your email I can send you a sample so that you can check it out

Have you tried vm part of my comment?