John Funk Community Champion

Great - glad we could help 

No. Go to Board settings > General At the bottom of the screen is a section called sub-filter 

Hi Jade, Basically, Anatasia would have to have Manage Sprint permissions on ALL projects used by the new filter. 

Correct :-)

Hi @aicha.cavazos - Make sure the user has the Manage Sprints permission in the Permission Scheme attached to the project. 

Yes, it makes sense. The problem is that you are using a Next-gen project which has those limitations. If you switch/migrate to a Classic Software project that uses shared custom fields, you can have more options in the list. We actually use an add-on called External Fields for Jira which allows us to link the dropdown…

Actually, that won't make sense because you can't see issues create after today. What exactly are you wanting to see? What is the scenario? 

Hi Jason - Welcome to the Atlassian Community! Are you comparing the createdDate to today? If so, try something like: createdDate >= startOfDay(32)

Es una especie de proceso de dos pasos. Una es crear el proyecto de "plantilla" que tendrá todos los esquemas deseados adjuntos: permisos, flujos de trabajo, notificaciones, etc. Tendrá que agregar personas manualmente al proyecto. Luego, puede tener algunas reglas de Automation For Jira que se ejecutan para crear el…

Hola Juan - ¡Bienvenido a la comunidad de Atlassian! Puede usar Automation For Jira para clonar problemas. ¿Puede darnos más información sobre por qué desea clonar problemas? ¿Por qué querrías dos del mismo problema que pueden desincronizarse entre sí?

Hi Calvin - Welcome to the Atlassian Community! I am not clear on what you are trying to accomplish. I see that you have added a field called Company. Are you trying to populate the list of values for that field? What exactly are you wanting to see? A report? 

Hi Lisa, 1 gray dot = 1 day 1 yellow dot = 2 days 1 gray dot with 1 yellow dot = 3 days 1 red dot = 4 days Then you just keep doing the math from there. Max is 4 red dots so those cars are a minimum of 16 days in that column. But you can always hover over the dots to see the actual number of days. 

Hi Margarita - Welcome to the Atlassian Community! I will check with Atlassian to see if someone can help you. 

Hello and Welcome, @Darshan Vaghasiya We are glad you are here!!

Hi Sascha - Welcome to the Atlassian Community! Check the sub-filter of the board to see if it is further filter cards out. 

You probably need to add the Due Date to the Edit screen and then try running it. 

Hi Valter, I have not seen that before. Can you post some screenshots of some examples? 

Just curious why it is no longer relevant. Did you get an answer?

Hi Orly, There is no option to do field level permissions in Jira Cloud. But a workaround might be to remove the field from the Edit screen for the project. Then create a new Transition screen with the field showing on this screen. Then create a new transition on the status that loops back to itself (called a Looping…

You create a project and set it up with all of the schemes you need. Then when you create a new project, use that project as the one you base the new project on. It will not copy all of the People information over, but it should be bare bones and not have all of the normal default ones. 

Quick filters are not going to show you what you need. You need to run this as a regular filter in the advance search mode: project = GATEWAY and status changed from "Open" to Backlog by lori.servies after startOfDay()

You are not going to be able to update a single workbook from two different filters automatically. You can run one filter and open in a workbook, and then run the other filter and open in a workbook, then copy one workbook into the other. That's about it. 

I will give this a shot and see what happens. 

Hi Darren - I would setup a base project the way you want it and then create all new projects based on that base project. Then you can deviate from there.

What do you get when you run the query? Did you replace the status name with your real status name?

Hi Lori, There was probably a step in the migration process that defaulted all of the current statuses to the Backlog if there were cards in those statuses that were not in the new workflow. If you don't map those (change from the Backlog) it will move them. When I first became an Admin I was not paying close attention…

Haha - I gathered that after I read through it again. I have the same issue with myself sometimes. :-) The most important thing is that it is working for you!

Look, I feel your pain as much as you do. I dislike the new view as well. In fact, I will be using it up until the day they take it way from me. My point is just that you know it's coming and that's not going to change. So until there are updates there are ways to use the tool as it is. Doesn't mean that we like it. And…

De nada :-)

Each issue can only be attached to a single issue security level. So it can't process both of them. Is there a reason my approach won't work for you.