Tuncay Senturk _Snapbytes_ Community Champion

Hi Pupie, I have reproduced and fixed the localisation problem. In a few days version 4.3.7 will be released. Thanks for your help Regards Tuncay Senturk

Hi Pupie, I have created an issue about this. You can see and follow it via link https://bitbucket.org/tuncaysenturk/jira-enhancer-plugin/issue/55/jep-436-custom-field-does-not-work-with Could you please provide me more info and attach screenshots in order to see where the problem is? I am waiting for your response to…

Hi Adrien, Did my comment fix your issue?

Hi Adrien, If you click on cog icon in SLA config page, you should see "Move" link. You can switch workflows using this "Move" link. Regards Tuncay

Hi Bill, We recently noticed your issue on our bug tracker system (related to this problem) and answered. Licensing features are handled via Atlassian API, and sometimes some clients face similar issues which can be solved after JIRA restart. Could you please try to restart JIRA? If the problem continues, you should raise…

Hi William, Sorry that I could not notice this question. Are you still facing this problem? Tuncay

Normally, there is nothing to do in upgrades. But in your case, after upgrading JIRA and addon, we will check whether JIRA uses AO_23ADAF or ao_ca2219 as table name prefixes. Please just backup your database, and export JIP data as json. But do not import it. We will use tables instead. This is the first case that we faced…

Hi, Sorry for the late response. The queries are OK, and as you mentioned it should work. Actually AO_23ADAF is the right name and in the feature updates, it will search for that. But when you upgrade to JIRA 7, we will do the same trick only once and I suppose, you won't need any more SQL updates

Hi, Thanks for the brilliant response. You already answered my latter question. We faced this problem before, and asked here: https://answers.atlassian.com/questions/15289760/why-do-add-ons-tablenames-change Then we raised this bug https://ecosystem.atlassian.net/browse/AMPS-1249 to Atlassian. No answer at all. How about…

Hi Daniel, I do not think your data has been deleted. Do you have database access? Could you please connect to database and see whether there are any rows in AO_23ADAF_JIP_INVENTORY table? Regards

Hello, You need to be JIRA Administrator to define SLAs. In JEP Field Permissions page, you'll find some JEP tabs or fields which you can restrict to specified user, group, role, .. I hope I was clear Tuncay

Hi Richard Check Enhancer Plugin for JIRA at marketplace. It has all fields that you asked for as well as any status field that you can create your own. Tuncay

Hi Jeffrey, Withn JIRA Enhancer Plugin, you can define your own "Time Between" custom fields for two states that you select. And you can filter issues by this custom field as well. Please see http://www.youtube.com/watch?v=gn9-RDrSkrw screencast to see it in action. Tuncay Senturk

Here is getting field and field valuedef customFieldManager = ComponentAccessor.getCustomFieldManager()def customField = customFieldManager.getCustomFieldObject("customfield_11300")// or // def customField = customFieldManager.getCustomFieldObjectByName("MySelect"))def fieldValue = customField.getValue(issue);

Hi Trupti, With JIRA Enhancer Plugin (since version 4.3.6) you can define your own "Time Between" custom fields for two states (built-in or your defined ones) that you select. And you can filter issues by this custom field as well. Please see http://www.youtube.com/watch?v=gn9-RDrSkrwscreencast to see it in action. Tuncay…

It is well documented in http://www.jiraenhancerplugin.com Under Documentation link there is a "Customization and Configuration" section. By the way, if you need any update on custom fields or any new feature, you may raise an issue by clicking the following link. I can improve the plugin by your demands.…

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". Regards

Hi Bahar,I faced the same problem and asked to Atlassian developer relations. You may show error message in the custom field area rather than disabling custom fields. So that customer will know there is something wrong with plugin's license.So, you have to check license validity on your custom fields actions and show…

Hi You can use Time to SLA addon. https://marketplace.atlassian.com/plugins/plugin.tts/server/overview

Hi Donncha, Sorry for the late response, I just noticed the question. Since "NOT and MET" are the reserved words for JQL please set different word for "NOT MET" ("EXCEED" as an example), then reindex JIRA. Then you can use "SLA Indicator" ~ "EXCEED" Tuncay 

Hi, I got the same problem with PostgreSql. I updated postgre jdbc driver to the latest one (9.4) and restarted JIRA Problem fixed

Hi, For this use case, you can't do anything. You've to have another custom field which returns a list of users who reopened the issue. I will think about it and may be in the upcoming versions, there may be a custom field which handles this use case.

Hi, User custom fields return only one User. So, if the issue has been reopened for a couple of times and reopened user is not unique, you won't be able to find all users. So you have to specify first or last. But, if the issue has been reopened once, the first and last reopened user custom fields will return the same…

Hi Shannon, You can define and configure a "Counter" custom field in JEP for your specific status.

Hi Bryan, JIRA Enhancer Plugin has a "Field Has Been Set" workflow validator. You can use it in any workflow transition. You can see documentation on www.jiraenhancerplugin.com Tuncay Senturk

Hi Allen, Almost everything that you mentioned is covered in Time to SLA Plugin. You can define as many SLAs as you want according to priority or even you can use JQL for SLA definitions. There is SLA notifier which notifies users (assignee, reporter, or you can set emails) when the SLA arrives time that you set (e.g. 2h…