Peter DeWitt Community Champion

Hi Milena, try this document: https://confluence.atlassian.com/adminjiraserver/setting-your-jira-application-home-directory-938847747.html It covers both Windows & Linux so use the Linux section and select your version of Jira from the drop-down. I'm not a Linux Engineer but if they are replicating the two nodes, my guess…

@Angela Williams, Jira does have a calendar but it's really meant for showing issues within a project or filter. https://confluence.atlassian.com/jirakb/jira-calendar-plugin-717456289.html You could think about have a separate issue type for time off requests and track them that way but it may become a bit unwieldy to…

Hey @Jon, Not sure if you have Jira Workflow Toolbox (JWT) but you should be able to do this with that add-on. There are checks for Boolean Validation as well and Field Initialization. You could simply use the isn't initialized check to accomplish this. -Peter

hey @duxw, what are you referring to using reuse with? We're going to need some more details on this. -pjd

@Samuel Chow, you are correct. Builds on an agent are sequential. If you need to run them parallel you will need additional agents. -pjd

@Andrea Mendez, Not that I know of. Beecom had one that was free but went paid last year. There are many add-ons that will provide this functionality but they are paid.

@sn, Just a thought, what if you created a new workflow with all the required statuses you and nothing else. Make sure each status has the allow all statuses to transition to this status checked and then replace your current workflow. Check the simplify workflow button after that.

@Clinton Smorenburg, The Linked Issues Section will appear when you link an issue to another issue or to confluence. It should appear down under description. As far as rearranging the view screen, that would require some Jira hacking and is not recommended. pjd 

@Kristen Riddle, Take a look at IssueSYNC from InTENSO. https://marketplace.atlassian.com/plugins/com.intenso.jira.plugins.synchronizer/server/overview pjd

Checkout Jira Workflow Toolbox: https://apps.decadis.net/display/JWT/Transition+issues pjd

Hmmm. Let me test it out here and I'll let you know.

Issues in the top navigation bar, search for issues selection.

@Mikael Skogstrom, I believe they are sorted based on rank value. I think you need to drag them into the correct order. pjd

@Scott McDonald, try createdDate <= -2555d

Since it sounds like your boards are filtering based on status this is the correct behavior. You would need to use a third party add-on like Script Runner or Power Scripts to automatically transition all sub-tasks to ready column when the parent is transitioned to that column. pjd

You issues need to be able to move freely from status to status. Essentially this means that each status should have the select allow all statuses to transition checked. This is the most common issue I see. pjd

correct

@Danielle (On leave until May 2025), On you Kanban board when you click configure you should see a saved filter under the general heading. Change the filter to include epics that are in a specific status. for example In Progress. Something like this: OR (issuetype = Epic and status = "In Progress" ) pjd

I can't think of any scenario in Jira where duplicate issues are listed in a query.

@Brian Franzen, open up your project, click the backlog, and create the new sprint from there.

And additionally, you will need the manage sprints permission for each project when a sprint contains issues from multiple projects.

@Bata, Sprints can contain issues from any projects within Jira even though they are 'assigned' to a specific project. Jira will automatically show other sprints that contain your project's issues. pjd

@Juliana Marcela Londoño González, If there is I still haven't reached it. You should be good to go with creating as many as you need.

@Aron Gombas _Midori_, Didn't even think of that add-on. Thanks for the addition.

@Joachim Schittenhelm, Sorry for the mis-understanding. That report is not going to key off of the sprints (they wont matter). What you will need to do is create a separate release for each team (sprint). For example, Release #1 - Team A & Realease #1 - Team B. This will let you essentially view each sprints work on this…

@Lukas Nosko, Are you talking about backing up Bitbucket Cloud to a local server?

That's the best we can do. I have mine on a number of features I'd like to see.

@Helen Makos, Unfortunately no. There is a feature request open with Atlassian here: https://jira.atlassian.com/browse/CONFSERVER-15619 pjd

@Joachim Schittenhelm, you should be able to specify what sprint you are looking at in the burndown report. We have 3 teams using a single project with 3 different sprints. The dropdown below should show you your current sprints as well as any past sprints. pjd

@Johnny Moore, Comment will get tagged to issues if the Issue key is in the Subject. pjd