Tuncay Senturk _Snapbytes_ Community Champion

Hi @Ionascu Irina You can create a Jira date custom field and set it via groovy script easily. If you are using Script Runner, simply create date custom field, add a script post function and set custom field date value using Groovy script. If you need help on writing the script let me know and I will try to help you…

Hi @Ionascu Irina @Iago Docando is totally right. You will need to use date field for the SLA End and set the custom field to the end of next business day programatically. However, as the product owner of TTS, I can announce that this is one of the backlog items, but I can't give an exact date now. Thanks 

I'm glad that it worked ;) 

Hi @Ya Liu You can do a search for SLA plugins for Jira Software by this link: https://marketplace.atlassian.com/search?hosting=server&query=sla You have to select the best one for your needs. I'm the product owner of Time to SLA which is top #1 used SLA plugin on Atlassian Marketplace. You can try it free and then see if…

Hi @Hitendra Chauhan Instead of flaggedIssue.setCustomFieldValue(flaggedCF, null); try this one IssueChangeHolder changeHolder = new DefaultIssueChangeHolder(); flaggedCF.updateValue(null, flaggedIssue, new ModifiedValue(flaggedIssue.getCustomFieldValue(flaggedCF), null), changeHolder) Tuncay

Hi @Lance Wilson As far as I understand you want to list issues in epics and you already have Script Runner. Did you have a chance to check issuesInEpics JQL function? For instance you can type JQLs as below: issueFunction in issuesInEpics("project = ACME and status = 'To Do'") issueFunction in issuesInEpics("key in…

Thanks @AliBurakEmener Team will soon get in touch with you.

Hi @AliBurakEmener , If you're interested in Time to SLA app, could you please raise a support ticket here so that our team would like to discuss details and let you know if it can be implemented soon. Cheers Tuncay

As @John Funk and @Ivan Lima stated, you can only use Service Desk SLAs with Jira Service Desk. You can;t use them with Jira Software. You need to use an app https://marketplace.atlassian.com/search?query=sla

Sorry, I don't have any clue

I'm glad to hear that 

Hi @Karl Edwards As far as I know 5.1.13 is not a valid maven-jira-plugin version (as you can see from the error). Here, you can find valid versions, or just use 6.3.21 as the version for your Jira 8 app. I hope it helps Tuncay

Hi @Ian Clem Welcome to the community. Those issues might be the ones that do not have any value yet. I mean, they might be either out of custom field context or they might be created before the custom field creation. You can add customfieldname IS NOT EMPTY to your JQL, or bulk edit issues to set default 0 value for…

Hi @ADSSA Jira Admin As far as I know, filtered group picker is not an out-of-box feature in Jira yet, even though filtered user picker comes with Jira 8.4 (AFAIK) There is a known issue which was created in 2016 and still in Gathering Interest status. You can watch/vote the…

Hi @Andrei Lavrinovich We need some clarification. First of all, the code snippet has some mistakes. 1. issue's status cannot be RESOLVED, FAILED and CLOSED at the same time, so you should change that as below if (["RESOLVED", "FAILED", "CLOSED"].contains(issue.status.name){ return (issue.getResolutionDate() -…

Glad to hear that

Are you getting null for jiraHelper? Where are you using this WebCondition? Can you give some details?

Hi @navya k You can't use JiraHelper by creating instance with new JiraHelper(). In order to get the issue in a class that extends AbstractWebCondition, you should override the shouldDisplay method as follows and use jiraHelper this way @Override public boolean shouldDisplay(ApplicationUser user, JiraHelper jiraHelper) {…

Hi @Steven Mustari You can only update select custom fields with an com.atlassian.jira.issue.customfields.option.Option, not a String. To get an Option instance, please follow below steps. - import OptionsManager import com.atlassian.jira.issue.customfields.manager.OptionsManager - Find appropriate option instance using…

Hi @Zeki Can KARATAŞ I'm one of the folks behind Snapbytes, and I'm answering as the product owner of Time to SLA app. Actually you can't bind related issue's date field but you can automate the process. If you define an SLA starting with Date field and update this field with the related issue you will be able to see…

You're very welcome

Please don't stuck in the code if it does not run as expected. As I mentioned before I did not test it. But I'll be here to assist if you need.

Hi @Henrik Åmark Sorry for the late response. And yes, you're 100% right, the year part would be a problem for my Jqls. And as far as I know, this can't be achieved without a script or app.

Hi @Henrik Åmark I think you should clarify a bit more. If you have a date custom field named Birthday and you have issue per person setting the Birthday, you can use jql like below: Birthday >= startOfDay() and Birthday <= endOfDay()

Hi @Stefan Updated field uses da/month/year format by default. To change this * Go to Jira Admin> System. * In the User interface section, click Look and feel. * Change Day/Month/Year Format to dd/MMM/yy h:mm a in order to see time part as well But keep in mind that this is not specific solution for Updated field but all…

Do you see the same behaviour for other issues?

Hi @Leirbag Assuab It seems to be a weird index problem. First, I'd recommend to index the project which is the faster than the system wide reindexing. On the other hand, you can check for other issues, and see whether it is related to the transition from Open to In progress. I faced some issues that the Re-index post…

Hi @Saaish Could you please accept the answer? Thanks

I'm glad that it helps.

You're welcome ;)