Tuncay Senturk _Snapbytes_ Community Champion

Hi Gil, In JIRA Enhancer Plugin there are built in counter fileds. You can define and set your own counters as well. Tuncay

Hi Jason, Are you still interested in this enhancement? Sorry that my watched labels did not cover those in this question. addon-plugin.jep is the right address. You can not use "today" in that area but you can raise an issue on our tracking tool so that we can change that matching field to JQL. Tuncay

Hi, This is a little hard and confusing but I will try to clarify. JIRA Issue navigator sorts according to index values, and indexing (changing) time value is nearly impossible because JIRA only indexes by issue status changes or by admin's reindexing. Since time changes every second, we can not index remaining time value.…

Hi, Could you please share Time Between configuration and the issue's history (All tab in issue main view)? Also, if you raise a ticket here, we'll soon fix the problem and you'll get notified about the progress. Regards Tuncay

Hi Ronglu, You're using very old version of JEP, this problem has been fixed in later versions of JEP. Thanks & regards Tuncay Senturk

Hi Richard, Enhancer Plugin for JIRA has reopening counter as well as Reopenings issue tab field. You can find detailed info for "Reopenings" here. Regards Tuncay

As far as I understand, you want to define a custom field which will keep SLA, and on any transition you want to change it according to another custom field. If these changes can be restricted with a workflow transition, you can use workflow post function to set SLA field by the custom field's value.

Hi Mohini, Time to SLA Plugin has additional parameter option for SLAs. You can define an SLA according to not only by priority and states, but also any criteria that you can add (e.g any custom field's value) Please see http://tuncaysenturk.com/timetosla.htmlfor detailed information. Tuncay Senturk

Hi Mike, As far as I know the only add-on that developed by Atlassian, about workflow is JIRA Workflow Designer Plugin. JIRA Misc Workflow Extensions plugin does what you say. On the other hand JIRA Enhancer Plugin has this workflow validator feature as well. You can see samples and screenshots on…

My bad, copy paste I changed the code accordingly

Can this help? def issueManager = ComponentAccessor.getIssueManager()def customFieldManager = ComponentAccessor.getCustomFieldManager()def cField = customFieldManager.getCustomFieldObject("customfield_id")def cFieldValue = issue.getCustomFieldValue(cField) issue.setSummary(cFieldValue + " " + issue.summary);

Hello Andrea, It is possible with Enhancer Plugin's Assign issue to the user in custom field post function feature.

Also please check the latest comment I added to your issue : https://bitbucket.org/tuncaysenturk/time-to-sla-plugin-for-jira/issues/84/same-problem-indicator-field-not-working

Hi Amanda, Check the last comment of this issue please. Adding another page for configuring indicator will be confusing for TTS users. In this solution, I offer to add another checkbox in SLA config page. If this checkbox is checked Indicator will show "EXCEEDED" if the SLA has breach, otherwise issue will be counted as…

Hi Amanda, Adding such configuration step may confuse users. I have plans to add slaId parameter to those JQL functions (starting with "tts.sla"), so that you will be able to filter them using JQL Tuncay

Hi Francois, Sorry for the late response. Generally if the issue is in a paused status, then the target date changes by time. However, both should work with latest version. Could you please check those issues using SLA Report? That report will give exact date and time values (SLA Target Date). Last, I think this issue…

Hi Francois, Sorting is done via indexing (Lucene Index) in JIRA. Since time changes every second it is hard to index, so we are indexing the target date. However if the issue is in paused times, the same problem re-occurs. We had some implementation to re-calculate and re-index within recent versions of Time to SLA. Are…

Hi Karan, Unfortunately after the license expiration you won't be able to use it. (Just like JIRA and all add-ons sold via Atlassian Marketplace) So, you will need to get 12 months maintenance license after expiration. Regards Tuncay

Hi Karan, Here are my answers. 1) If we purchase your license for 2000 users, the cost is it once off or yearly? The price is yearly. But the following years the price is halved. For instance for 2000 users, the price is 1400$ and the upcoming years you'll pay only 700$ 2) If we upgrade to 10000 users, do we just pay the…

Hi Amrusha, I could not understand your question. If you clarify we can try to help you. If you need notification to users before breaching, there is SLA Notifiers that you can define as many as you want so that it notifies users, groups you defined. Regards Tuncay 

This question is discussed here. There is an issue JRA-9363 which has been created in 2006 to define a workflow to be default one for new projects, but still remains in OPEN state Tuncay Senturk

Hi David, At the moment you can not do that but if you raise an issue to our tracking system it may be added in the upcoming versions. Tuncay

Hi Karan, Thanks for your interest. You can add additional JQL to SLA definition. So you can type Product Type = X and Priority = Major to JQL text area of the SLA definition to apply the rule. Regards Tuncay Senturk

TTS v3.3.3 has a bug fix for this issue.

Hi Wladimir, Finally I found the root cause. If plugins are using same class name for configuration, one plugin overrides the other and cause problems. I raised a ticket to Atlassian about the topic. However, I will not wait for Atlassian's solution, I will soon release a new Time to SLA plugin version fixing this problem.…

Any progress on this? I have tried and seen the success scenario. If you have any problem please do not hesitate to ask Tuncay

Hi Daniel, Here you mean two assignee action. However you can do it with JIRA Enhancer Plugin as below steps. 1. Add "JEP - Assign Issue to a Role" post function. Here all issues will be assigned to Role B (has member of User B). 2. Add "JEP - Assign issue to a role, according to a field of issue" post function. Select…

Hi Daniel, Please email me with screenshots so that I can reproduce and help you tuncay.senturk@gmail.com

I have implemented already, and this feature will be live within two weeks

Hi, JIRA Enhancer Plugin (from 4.3.5 version on), has a post function "Assign to a user in role according to a field in the issue". It automatically assigns issue to a user in a role based on a field in the issue. However, it does not assign within creation of the issue. But in the upcoming version it will. Regards Tuncay…