Tuncay Senturk _Snapbytes_ Community Champion

Yes, that's how it may work. It starts the job and run in the background. In order to run it foreground execute below command. then you will see the logs in the console, not sure why you can't see those log files though start-jira.bat /fg

You have to provide more information. The full screenshot where we can see the error message and/or the related section of the log file (atlassian-jira.log)

Edit your workflow and select the transition to the "Done" or "Canceled" status (for example, the transition from "In Progress" to "Done") Then click on the transition arrow and select Validators. Add Validator, then select ScriptRunner > Script Validator (I assume you have ScriptRunner) Use the following Groovy script to…

Hi @MidnightExe To achieve this in Jira, you can use a Workflow Validator instead of a Trigger or a condition. A Workflow Validator allows you to check conditions when transitioning an issue, and if the condition isn’t met, it displays an error message while keeping the transition button visible. Workflow condition hides…

That's strange. Does your start-jira.bat or set-env.bat file have any other location for the log files? I'd recommend checking the bat file.

Hi @Salam Elias If Jira starts without errors but is inaccessible, you should check application logs (not the console logs). To do that, navigate to the logs folder in your Jira installation directory (E:\Jira Software\logs) and open the atlassian-jira.log file. There should be something there. Look for any errors or…

Hi @thumuluru.shreya You can use Send Web Request action to create a Confluence page using the Confluence REST API and fill data from Jira as well. POST - https://<your-domain>.atlassian.net/wiki/rest/api/content In the request body, include the details of the Jira ticket by using smart values. Here is a sample { "type":…

Hi @Jose Ramirez I am not sure but this may be most probably because how you handle empty or null values for the INITIATIVE_NAME field. When it is null or empty, the rendered string becomes something like INITIATIVE_ID - null. I'd change the renderOptionHtml function as below renderOptionHtml = { String displayValue,…

Hi @Michael Kornatzki Above I mentioned both, ChangeHistoryItem has getFroms and getTos but if you use <span><a href="https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/issue/changehistory/ChangeHistory.html#getChangeItemBeans--" target="_blank" rel="nofollow noopener…

No, you will only remove the Original Estimate from the edit screen, this way it will not be editable by any user.

I grew up without either a live or artificial tree. For the past 6-7 years, we've used an artificial one. This year, we decided to try a live tree, and it's been the most enjoyable experience so far. Despite the extra effort of cleaning needles and watering, it's definitely worth it!

Hi You can remove access for other users to edit the Original Estimate by removing it from the Edit Issue screen. This will prevent them from modifying it via UI. To restrict access to only admins, you can create a transition (to the same status) that includes the Original Estimate field on the transition screen. This…

Yes, it is possible to version control your ScriptRunner scripts in GitLab (or any other Git-based system). If you use ScriptRunner scripts as text-based Groovy files rather than using directly in the app, you can store and manage them in a Git repository. All you need to do is create a local directory to organize your…

Hello @Amruta Harale Yes, you definitely need to configure the gadget by selecting at least a project or a filter to see the average age calculation.

Hi @Pamela Gustavson Have you checked if the Supervisor custom field has different configurations for onboarding vs. offboarding issues? Go to Contexts and Default Values and ensure the field is available for the Onboarding Issue Type and project. Other than that, I can't say more as I need to see the request payload.

Hi @Patil Vikas What results are you getting? Could you please explain further?

Hi @Nour Dandan This is a common scenario when integrating external systems with Jira. I listed the steps below that I'd follow to achieve such an integration - create a custom Field in Jira (name it as CRM ID) - send this CRM ID during the issue creation (or update) URL: /rest/api/2/field body: { "fields": { "summary":…

I don't have specific December memories, but I know that many people cherish this time of year. Some enjoy decorating their homes, while others go on holiday for winter activities, and I was always jealous of them. Your tradition of lighting candles each Sunday in Advent sounds like the most creative and practical way I've…

Hi @Diego Martínez You can do that with Jira Automation. You can define a trigger with a condition Issue Type equals Epic, then select a branch rule related issues: parent issue. Use the Parent issue as the branch condition. This will allow the rule to work with the parent Initiative linked via the Parent Link field. Add…

You're welcome!

I am not sure but did you try also formatting the version? {{version.releaseDate.format("yyyy-MM-dd")}} equals {{now.minusWeeks(1).startOfWeek.plusDays(2).format("yyyy-MM-dd")}}

Is this escalation service job your own script? If yes, are you using Atlassian cache in that code/script? If not they cannot replicate data between nodes.

Hi Thinh Le, Did you try omitting the formattedDate property entirely or explicitly setting the date object to null? { "editedFieldsInput": { "datePickerFields": [ { "fieldId": "duedate", "date": null } ] }, "selectedActions": ["duedate"], "selectedIssueIdsOrKeys": ["10309"], "sendBulkNotification": false } 

Hi @Lydia I assume sub-tasks are globally on as there are projects using sub-tasks. (Jira Settings > Issues > Issue Types >Sub-tasks) Ensure that sub-task issue type is already included for that project (you don't have sub-task option) under Jira Settings > Issues > Issue Types > Issue types)

Hi @Naveen kumar I don't know what you're seeing when you run the code but I'd change it as below to update labels without overwriting existing ones. def customFieldA = getFieldById("customfield_25202") def labelsField = getFieldByName("Labels") def customFieldValue = customFieldA.getValue() def existingLabels =…

Hi @SyedAhmedKabeer Yes, it will automatically be replicated to node 2. Cache data replication between nodes is managed asynchronously. It means that, when data is stored in the cache on Node 1, the modification is replicated to Node 2 with a possible slight delay. Here is the official documentation regarding the cache…

Apologies for my delayed response. Yes, you can accomplish this using Automation, and I explained it by using a Send web request.

Hi @Alexandr In Jira Data Center, the built-in "Create Version" action only supports limited fields (version name and release date). To include additional fields like start date and description, you'll need to use a web request with the Jira REST API. URL: https://your-jira-url/rest/api/2/version method: POST body: {…

You're welcome!

Hi @Fleur Post You can achieve that if you have Script Runner or Enhancer Plugin. If you have Enhancer Plugin, you can easily define user custom fields which can be user who did which transition but if you don't you can store those users adding post functions in your transitions. Let me explain step by step. * Create…