John Funk Community Champion

Hi Mark, My experience is that it doesn't really matter if you choose too many statuses in the list. Your workflow will know the right one to check at the time. I would just cover all of my bases and move on. :-)

Hey Phil - 1. You might try reporter = currentUser() 2. I would suggest you modify the screen configuration.

Hi April - Welcome to the Atlassian Community! See this document for more guidance, but it sounds like you need to adjust the Manage Sprints permission in your Permission Scheme. https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html Hope that helps!

No problems with me either. 

Administer Projects

Hi Fernando, Yes, you need to have a project role permission that allows you to Administer Projects in the Permission Scheme for that project. Typically, that is the Administrator project role. 

Sounds like you are wanting to order the issues inside the swimlane. Is that correct? You can do that with the ORDER BY function (ORDER BY Status Desc) at the end of your query. But realize if you do that you will lose the ability to drag the cards up and down to re-prioritize. 

Hi Phil - Welcome to the Atlassian Community! By default, the reporter should be populated with the current user. Is that not happening? Second, yes, you can modify the Create screen to have a smaller number of fields for the user to see. 

Hey Brandon - Welcome to the Atlassian Community! You would need to create a second Swimlane with the different JQL for each Swimlane. That should accomplish what you are looking for. 

This is probably a good place to start :-) https://confluence.atlassian.com/jira062/configuring-workflow-588581847.html

Yes, you would have to define each swimlane individually and manually. The hope is that those queries wouldn't be changing that much.

Hi! Columns are based on (mapped to) statuses which are a part of the workflow. If you need different columns, i.e. statuses, just modify the workflow. 

Hi Michael, Certainly Jira can do that. You won't have swimlanes in your Backlog, but definitely on the board. Each swimlane is based on a JQL query, so just determine what those filters will look like for each swimlane. 

Hi James, Cloning an issue should automatically create a link between the two issues. It should be in the Linked Issues field. And/or you could also create a custom field and copy the key from the original issue into the custom field of the second issue. 

Yeah, you would probably have to do that 1,000 at a time. So, I guess it becomes, which one is faster - or less painful :-(

So sorry. You might try posting the question on this thread: https://community.atlassian.com/t5/Jira-articles/Becoming-a-JIRA-Search-Ninja-History-searches-in-JIRA/ba-p/461943#U793004

Hey Michael, You might could export as CSV, update the values to match user names and then reimport. 

:-( Maybe try summary ~ "_psf~"

Not sure I see a problem there. ;-)

We use a free Chrome extension called Better Jira. Not sure if that will help you or not. But I don't experience the problem - the headings just move down with the Quick Filters. Also, why so many Quick Filters? Maybe create additional boards with less Quick Filters on each? 

Maybe try summary ~ "psf~"

Hey JHicks, You will also need the site-admin role/group to be able to manage users. 

Nothing like the Big Green Egg! Smoked 5 racks of ribs on the 4th of July and feed lots of hungry family and friends. :-) Next day it was burgers and dogs. Great flavor and moist meat!

Oops - yes! Thanks!

Hi Sridhar - if you share your filters with your team (or even with Public), they should be able to find them and use them. They can just do a global search on all filters. You might want to do some type of naming scheme to help them, but they can even put your name in as the Owner to help narrow the search. 

add this at the end of your filter: ORDER BY status ASC

Great! Can you go ahead and click on the Accept answer button to close the issue?

Hi Sue - are you using Server or Cloud?

Hi Chi, You can run a filter, then do a Bulk Change - Edit. But first, you need to make sure that the same Component is available on all projects that the filter will run against. 

Sorry for the long delay. I am not using Jira Server so I cannot duplicate. I would suggest you enter a support ticket with Atlassian. Sorry.