Tarun Sapra Community Champion

Please accept/upvote the answer if it works for you. thanks.

Yes, it's doable, you add a column for issue id and add the existing issueKey in CSV so that while importing the issues, all the issues become sub-tasks for the existing issue. Possible duplicate - https://community.atlassian.com/t5/JIRA-questions/CSV-Importing-of-sub-tasks-and-linking-to-existing-Story/qaq-p/224226

Hello Brenden, I ran into a similar issue few months back, few things are important here 1) Please make sure the cloud backup is for the "Server" version of JIRA and not for "cloud" version of jira. 2) JIRA cloud version are always latest versions, thus if you are trying to restore the backup on the server, make sure…

Sure, could you please accept/upvote the answer if it works for you.

I have updated the code in the gist link and it should remove some of the compile errors, but for the rest you have to go through the code and update as per your workflow and transition ID.

You can't use the exact same code, as the code is a reference which is using the "transition" id of close for sub-tasks but in your case you have to move the sub-task from waiting to "To do" thus you have to use the transition ID of your workflow and change the code as per your requirement.

The create button whcih you are clicking is for issue creation and not for project creation. It seems you don't have JIRA admin rights. Here are the parallels as per my opinion. Project = Project Epic = Release Requirement (so that it can be broken into stories) Story = Business requirment (generally shouldn't be more than…

Welcome, please accept/upvote answer if it answers your query. thanks.

Yes, your team can have a dedicated ScrumBoard in the JIRA. You can set permissions such that the board is readable/editable only by your team. But this ScrumBoard will be using an existing project/projects . Thus you can't have a dedicated Scrum Area wherein you can create projects. Because in JIRA anyone with admin righs…

Iteration review is same as Sprint review.

Date compare is supported by means of plugins like Script Runner's JQL functions in JIRA https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_datecompare

Hello Vernon, Comparing dates isn't supported yet by the JQL in JIRA. Please see the following links https://jira.atlassian.com/browse/JRASERVER-20727 https://community.atlassian.com/t5/Questions/Is-it-possible-to-compare-date-fields-using-JQL/qaq-p/37331…

Hello Janath, The list of meetings you have mentioned is pertaining to Scrum way of working and it's correct. Here's an artcile about the same from a senior Agile coach. https://www.atlassian.com/agile/ceremonies

Hello Vmaz, In JIRA, Project is the core entity which is made up of lot of different things, and issueTypes like Epics , Bugs, Stories are part of the project. Technically Epic can't be Project in JIRA as Epic is an issueType which is part of Project. Thus, you need to add a project and then add issueTypes to it.…

But this is more easy and straightforward without hardcoding the status in code. [$issue.status]: ($issue.key) $issue.summary

Well the answer you have shared has the exact same link which I have shared as the top voted answer. I don't know where the confusion is. As, you just have to edit the template and thats it. As far as coding is concerned then since your requirement is to append the current workflow status in the subject line thus you would…

In the old version the velocity templates might have been modified. When you upgrade to the new version you have to manually take the backup of oldvelocity templates and set it for the new version. Customizations are not automatically upgraded while upgrading JIRA.

JRIA out of the box doesn't provide way to filter on roles, the JQL tricks plugin provides to filter based on current state but your requirement is "was in" thus not only current but past as well. Hence right now I am not sure about it, I will come back to you if something comes to my mind.

For the part "tickets assignee changes in last 5 days" you can try this , as it's working assignee changed DURING (startOfDay(-5),now()) 

Hello Alana, It seems that you are using JQL tricks plugin, (usersInRole) function. From the docs it seems it supports only "in" operator and not "was in" operator as was in operator searches the history of the issue- usersInRole([project],role) Function To find issues based on users in a specific role in a specific…

Hello Venkata, I would suggest you only modify issueUpdated velocitytemplate as you want to include issue status in the subject line and for issue create event it doesn't matter as at the time of creation of the issue the status is open. Thus, you can modify the issueUpdated.vm file and since issue object is present thus…

Hi Venkata, The Above documentation explains all that is required. You need to work with someone who has access to the server where JIRA is deployed as you need to modify files present in the "installation directoy" of JIRA on the server. The system information section of jira shows the path to installation directory on…

JIRA generates emails in reaction to events using a templating engine. The templating engine is Apache's Velocity. This is a relatively easy to use templating language that can pull apart java objects in useful ways. The mails are generated inside JIRA by invoking Velocity with a set of objects of relevance to the event.…

From the 7.4 release notes If you're a board administrator, you can turn on the Kanban backlog by accessing your standard Kanban board and selecting Board -> Configure > Columns. There you'll see instructions on how to set up your Kanban backlog, and how to disable it if it's not something your team wants to use.

You would need to customize the velocity templates. Please see here https://confluence.atlassian.com/adminjiraserver073/customizing-email-content-861253783.html Also, in the velocity template you have the issue object thus from issue object you can easily extract the status and put in the subject line of email.

please see here for complete instructions - https://confluence.atlassian.com/adminjiraserver073/customizing-email-content-861253783.html Also, there is an open issue about the same requirement as yours https://jira.atlassian.com/browse/JRASERVER-3609

This requires modifying velocity templates.

Some samples for validation scenarios using "Script runner" plugin - https://scriptrunner.adaptavist.com/4.3.4/jira/recipes/workflow/validators/simple-scripted-validators.html For plugins go here - https://marketplace.atlassian.com/ 

You will need a plugin to implement it in a single transition, it's pretty straightforward. Within in a single transition you can achieve this functionality using following plugins - you can use Script runner plugin or Automation plugin or JMWE plugin for achieving 

Event notifications are based on "Issue event" like Issue Updated, Issue Moved etc, thus, the mails sent are based on the issue event and not field event like priority. Hence by default if the issue is updated whether it's priority or any other field like description then "Issue Update" notification will be triggered and…