John Funk Community Champion

Hi Jim, Does the board use a filter that has multiple projects in it? Are you a project administrator for all of those projects if yes? 

Hi Diane - Welcome to the Atlassian Community! When you say that you can't add someone - do you mean that you can't assign the card to them? Or something else? If that, check the Permission Scheme for that project to see if you have the Assign Issues permission. 

Are there other issue types in the issue type scheme for the project? If so, I would go ahead and open a support ticket with Atlasssian: https://support.atlassian.com/contact/#/ Please post back here after you get a resolution so we can close this one out. 

Hi Amanda - Welcome to the Atlassian Community! Yes, you should be able to do that. When you are in an Epic and select Deep Clone, you will get a pop-up like this: So as you see, you can clone the Epic and all of the children. 

Yep, you can use issue types as well. You might consider creating a Group in Jira User Management for each team. And then populate the group with the people in that team. Then you can use the Group for sending emails, notifications, etc. Then create a custom field of single group picker type. Use that field to assign the…

Hi @imtiaz.ali , Have you checked the Permission Scheme for the project to see who can see the project? Also, check the project roles to see if the team member is included in that somewhere. Just because you can add them as a Component lead doesn't mean they have access to the project. Although it probably should!

Hi Deepak - Welcome to the Atlassian Community! Workflows (and custom fields and other things) are not shareable with Next-gen projects. You have to re-create the object or workflow for each project. If you need shared workflows, it is better to create Classic Software projects. 

Hi Chris, I don't have answers for all of this, but a few questions for you first, haha. How are you capturing which team works on the issue? Do you have a separate custom field where you record that? If not, that would be my suggestion. Then you just include the value of that field in the filter for the Queue. 

Hi Maciej - Welcome to the Atlassian Community! Can you share a screenshot of that? Do other users also get the same error? Have you tried with a different browser?

Hi Kunal - Welcome to the Atlassian Community! There are a couple of things you can check. First, look that the Field Configuration for that project and issue type to see if the Task Template field is marked as Required. Second, look at the workflow for the Defect issue type for that project. Check the transition for…

Hi Eric, Not sure if this would help or not, but you might try with a larger monitor, or decrease the resolution of you browser view by pressing CTRL - (CTRL MINUS) a few times to see if it gives you more fields to see. Then you can press CTRL 0 to return to normal size. 

Rats - bad guess - sorry! Let's see if this is any better: Hallo Eric, Ik probeer ook op bepaalde tijden op te ruimen, maar ik heb niet de bandbreedte om dit zo vaak te doen als ik wil. Ik denk erover om hier elke maand wat tijd voor uit te trekken. Dit is een van de tools die ik heb gezien en veel aanbeveelt om hierbij te…

Also, can you click on the Log de auditoria and send a screen shot of the details for latest one that failed? 

Hello and Welcome, Tim! We are glad you are here!!

Hi Tiffany, Try this: status was not Done BEFORE "2020/11/30 12:00"

Hallo Eric, Ich versuche auch zu bestimmten Zeiten aufzuräumen, habe aber nicht die Bandbreite, um dies so oft zu tun, wie ich möchte. Ich denke darüber nach, jeden Monat etwas Zeit dafür einzuplanen. Dies ist eines der Tools, von denen ich gesehen habe, dass sie viel empfohlen haben, um dabei zu helfen, obwohl ich es noch…

Hi Jeff, You can add a property to the transition in the workflow to add the Opsbar sequence to set the order https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/

Hi @Kiruthika - All that the pinning of fields does is moves the fields to the top of the list. So if you need that for all users on that project, then just edit the Issue Layout and move the fields up in the order. Go to Project Settings > Issue Layout Then choose the screen you want to modify based on the Issue Type.…

Hi Rohin - Welcome to the Atlassian Community! I don't think I have ever seen an error like that in an inactive workflow. Maybe try to copy the workflow and see if you can change the copy. 

Not that I am aware of, but you can follow the Next-gen releases and roadmap here: https://www.atlassian.com/software/jira/whats-new/next-gen

@Yaniv Kalif - Did this get your question answered? If so, can you click on the Accept Answer button above so we can close this one out? 

@Shira Izon - Right now there is not a way to share the Issue Layout across multiple projects. But here is a feature request to do that which you can vote for and follow: https://jira.atlassian.com/browse/JRACLOUD-71630

Hey Aron, Then you can use a JQL condition that looks like: Project = ABC and status changed to "In Progress" during (2020-01-01, 2020-01-31)

Hi @Dario Erregue - Just following up with you. Do you still need assistance with this? 

No Jira Administrator is the top position. Try it out with a user for site-admin as their only group 

For the advanced roadmap feature, go to the top navigation bar and click on Plans.

Hi Katie, We use different statuses depending on what is happening with the card. Done - finished and completed Discarded - We have not started it just and are not going to do it it ever Aborted - We have started it but decided we are no longer going to do it ever. Abandoned - We have started it but not going to continue…

Hi Katie, They can add themselves as Watchers on the project, which should have them receive notifications. 

Hi @Anni Bäck - This was posted a long time ago and has no resolution. Are you able to do what you needed?