Matthias Gaiser _K15t_ Community Champion

Hi Tibor, which version of JIRA are you using? In JIRA Cloud, I was unable to reproduce your behavior. I could think of two ways: * Change them back to stories, remove the epic link and change them back to epic. * Use the REST API "Remove issues from epic" to remove all the issues from the epic you do not want to have in…

Hi Agung, yes, this is possible - you just have to follow the installation instructions described here. For Azure, you might want to have a look in this (older) blogpost to see if sth. like this works for you. Cheers, Matthias

Just in case you are still looking (or someone else is looking like me), you can get all the boards valid for a project with the same request to get all boards (see https://docs.atlassian.com/jira-software/REST/cloud/#agile/1.0/board-getAllBoards). You just have to specify as query argument (projectKeyOrId) your project.…

There is an inofficial REST API provided by JIRA's project-config plugin you can use: * You can retrieve the workflowscheme with this call: JIRA_BASE_URL/rest/projectconfig/1/workflowscheme/PROJECT_KEY * The workflow can then be retrieved using the workflow name by one of the following endpoints:…

Hi Mukul, 6.4.14 is the latest version of JIRA 6.4, see the release notes here. After 6.4.x, Atlassian started with JIRA 7.X, you can get the release notes for JIRA Core here and for JIRA Software here. Is there any specific reason why you update to 7.2.8 and not to the latest JIRA 7.3.4? Cheers, Matthias.

I'd also be highly interested in that feature. Is there a public JIRA project where we can watch this ticket? Or will you update this question as soon as it is released?

You could just choose a cascading select field if you create the custom fields yourself.

Hi Negar, if I understand you correctly, you want to sync issues between two projects only if the ticket belongs to a specific component. It is possible to sync issues like this with our sync solution - Backbone Issue Sync for JIRA. You can simply filter the issues to be synced by specifying a JQL, e.g. "component =…

I had the same question (and confusion) some time ago. 

See this article from the JIRA documentation for marking epics as done: https://confluence.atlassian.com/agile/jira-agile-user-s-guide/working-with-epics/completing-an-epic

Hi Lokesh, I think this Atlassian answers article is the right one for you. Matthias.

Hi Laura, I don't think there is a solution to do this without an addon. (@other readers: Please correct me, if there is). With our addon, you can sync tickets between instances. So, we do not offer a way to access the other JIRA instance, but to create local copies of the tickets of the other JIRA and keep them in…

Hi Laura, the question is what do you mean with "share data". If you have some issues that people in both JIRA instances would like to work on or at least to be informed, then you probably want to set up some sort of a synchronization between these JIRA issues. In order to setup such a synchronization, you could use our…

I know this question is some years old, but in case, you also get the error and a clean does not help you: It might be the case that you have an old log configuration for JIRA 5.x in your plugin which you should update and replace the MultiTenantJiraHomeAppender by the JiraHomeAppender. This article states that for JIRA 5…

Which version of JIRA are you using? I checked in a JIRA Server 6.2 and also on a JIRA Cloud instance and they both have a "Field Required Validator". See below list of validators for my JIRA Cloud instance. transition-conditions.png

Hi Courtney, I'd recommend you to make it required on the create issue transition as described in the JIRA knowledgebase. You can see also this question for more answers. Cheers, Matthias

You can set the language also in your user profile. Have a look in the confluence or JIRA documentation. The same is valid for JIRA. That may be also the reason why you don't see a language change when you've changed the systems default.

Basically, this question is about tomcat administration. It is perfectly fine to change the name of the service tomcat is running with. In order to change the name and many other options, you can simply follow the general tomcat administration guidelines: https://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html…

Hi Jorge, it is possible. For details on how to do it, see this documentation from Atlassian. Matthias.

You can do a two step solution:* Get All issues for defined version Use the JQL search REST API with a JQL like "fixVersion = 1.0" * Transition history for these issues Use the get Issue REST API with expand=changelog e.g. http://{{serverUrl}}/rest/api/2/issue/PA-18?expand=changelog Or all in one call: * Use the JQL search…

I know this question is fairly old, but if someone else is having this problem. The answer is simply, yes. When you setup the synchronization for a versions field, you have the option to "create missing versions". Please make sure that the technical integration user needs the "administer projects" permission in order to do…

Hi Caleb, have you seen this post? The basic question is: Do you have a screen defined for your transition you are trying to perform? If not, you should add a screen with the comment field on it as described in the JIRA knowledgebase. Hope this helps! Matthias.