John Funk Community Champion

Right - if they are not in the Backlog status, you have to put the status in a column for them to show up on the board. But they won't show up in the Backlog if they are not in the backlog status

You can't - theoretically, if it is an active Sprint, then there is no Backlog - only active issues being worked as a part of the Sprint. Your Backlog still exists - but is not on the actual active Sprint board itself. See screenshot. Now, one of our teams has a "Backlog Pullable" that exists in the first column that…

Well, one note is that the Reporter field is updatable - in other words, if someone is creating an issue for another person, just change the name of the reporter while the issue is getting created. Or like I said above, base it on the value of the Epic. 

In that case, you should probably capture the value for the Dept field in the Epic and then let the tool copy that value down to the individual stories/issues. 

No, Backlog is just a status and could literally be placed anywhere - it's up to your team for implementing best practices. Also, it depends on your workflow - typical workflows have issues going straight to the Backlog status for Software projects, it it could go to another one. Ya gotta start somewhere and backlog is…

Gotcha ;-)

Hi @Zach Dimond Your best bet would be to use some type of Marketplace App like Automation for Jira or JMWE or ScriptRunner to accomplish that. If you just use the custom field that you have already created for Dept, then use that value, that should work. What is so time consuming for the user to populate that one field?

Hi @NS - yes, you should be able to create a Quick Filter that uses a JQL statement such as: status != Open (or whatever the status is which is mapped to your ToDo column. You could label it something like Hide Open. We do that with Hide Done on our boards also. 

Sorry, but I am still not understanding the problem - I don't know know what you mean by "not visible in the lookup" - which "lookup" are you referring to? Have you tried looking at the issue in the Old Jira Issue View to see if it makes a difference. 

Hi Jim, The status has to be on your board somewhere for the issues to show up, even if the issue is just in a Backlog column. So, having said that, our teams have created a Backlog column as the first column on the board. Then you can even have a To Do column or whatever you want for items that have advanced past the…

The data will only get corrupted if you have issues in a status in the current workflow that does not exist in the workflow you are moving to. You can easily do a search on those and even download to a spreadsheet so you can see which ones are affected if something goes wrong. Much simpler than trying to recover a backup…

Hi @Prashant - Welcome to the Atlassian Community! Is there a question that you have? 

Hi @Arvind Sinha - Welcome to the Atlassian Community! 1. To delete issues, you must have privileges to do that in the Permission Scheme connected to your project. Check the scheme to see what roles or groups can do that. You do not have to be a Jira Administrator to see that or to delete issues if you have the permissions…

Hi Hammad - Workflows are associated with projects, not sprints. And then the sprints are associated with the project. If you have a sprint that spans multiple projects, all projects will need to be linked to the same Workflow Scheme. Your sprint board is then linked to the statuses that are in the workflow scheme. You can…

Hey Michael, Hopefully, the diagram from Jack was helpful. In addition, for the specific case you have, you need to create a screen and associate it with the particular Issue Type via the Issue Type Screen Scheme - which is at the bottom of the diagram. 

Hi Michael - If I understand you correctly, you would like to create a new issue (issue B) when a new issue is created for New Hire or Termination (issue A). And then have the two issues linked, I assume in the Linked Issues field. Does that sound correct? Yes, that is possible with a Marketplace App but not native Jira.…

Hi Hector - Welcome to the Atlassian Community! No, it is not possible to create an issue without a Project. You could create an "Unassigned Project" project and have issues created there. Then you can do a move to the appropriate Project later. 

Hey Louis - I rarely do the backup unless it is a MAJOR change that will affect thousands of issues. And in cases like that, I usually just create a copy of the Workflow, make the changes in the copy and then implement the copy. Then if it all goes awry, I can put the original back in place. 

Hi Mario - Welcome to the Atlassian Community! You receive the message on the workflow because you are probably trying to add a transition to a status that doesn't already have an outflow. It's just a quirk within the tool. To make the change to add the transition in this case, you will need to make a copy of the Workflow,…

You can also use a gadget on a dashboard to do a count for you for the rows returned from each filter. 

The closest you might be able to come is to link the Roles to a Group, then you have just one change to make for each Role for each new Project. Then maintain the common people in the Group. That way you don't have to put individual people in everytime.

It's not going to be able to do that directly. You might try this: issuetype = Bug AND Status changed FROM Open TO "Reopen" DURING (2019-09-01, 2019-09-30) and then run again for: issuetype = Bug AND Status changed FROM Reopen TO "Open" DURING (2019-09-01, 2019-09-30)

Translated Diallo's question to English using Google Translate: Hello I use Jira software, I create a project for managing the activities of all employees of the management. Is there a way to have a project closed down by default to users, but I can ONLY assign users access to particular tickets? And my response: Hello…

I believe I have already answered double or triple the quota just this morning hahaha.

Community has been the most helpful resource for me as I learned Jira and got up to speed. I then wanted to give back to the Community by helping others with their needs by answering some questions and providing advice. The benefit goes both ways, and I encourage you to answer when you can!!

Hello Diallo - Bienvenue dans la communauté Atlassian! Pour qu'un utilisateur puisse voir les problèmes liés à un projet, il doit disposer de l'autorisation Parcourir le projet dans le schéma d'autorisation associé au projet. Ils doivent également disposer du privilège Utilisateur assignable pour que des problèmes leur…

Hi Pooja, If I understand you correctly, you should be able to write a JQL that will show the issues that have had a status change (even for a particular time period). SOmething like: issuetype = Bug AND Status changed TO "Reopen" DURING (2019-09-01, 2019-09-30) If you don't want the time period, simply drop the part…

Hi Karamba - can you provide some screenshots?

Hi Simon, I have the same need. I create a project based on an existing project, which attaches the schemes as I want. But I have to go back and add all of the people. Here is the link to a ticket in Support for this, but it only has a couple of people watching. Maybe you can vote for it. :-)…

Hi Rajiv - Statuses are sort of attached to a project in that the statuses are a part of a workflow and the workflow is attached to the project. But all projects must be attached to a workflow, and therefore, must have at least one status that should show up in your dropdown. And the other thing is that you can see the…