John Funk Community Champion

Hi @usman_malik - Did the responses answer your question? 

Hi Aldrin - Welcome to the Atlassian Community! What kind of errors are you getting? Or what exactly happens?

They should explain to you why that is the case. It is certainly not Kanban principles. How are they implementing a pull system using Kanban?

Hi Cristina, I would say yes, but you should test it out to be sure. First though, the user must have the ability to Set issues security in the Permission Scheme. 

Yes

Hi Nita, That sounds very weird - you should immediately open a support ticket with Atlassian to find out what is going on. Please post back here with the resolution for future readers. https://support.atlassian.com/contact/#/

Hi Pradeep, I would open a support ticket with Atlassian. Sometimes email addresses (and maybe even domains) get blacklisted for some reason. https://support.atlassian.com/contact/#/

So your Condition above does not work? Try changing the Comparison Type to Date without time instead of String. 

Hi Sandeep - Welcome to the Atlassian Community! I would use Project = ABC and created >= startofMonth(-1) and created <= endofMonth(-1) Because some months have 31 days and some 30 days and one 28 or 29 days. The code above will get the previous month. 

Hi Rafael - What's the reasoning behind this? The user already has access to all of the cards on the board. The Quick Filters just narrow down from what they can already see, so it wouldn't make sense that some Quick Filters are hidden. 

Hi Varun - Welcome to the Atlassian Community! You should be able to edit you workflow so that the there is a transition from the status where it is awaiting for approval to go to a new Waiting for Customer status. Then edit the Approval criteria to go to that status instead on a Decline. 

Well, bottom line is that the Resolution should not be on the Default screen at all! (Or Create/Edit/etc. You should do what is mentioned above, a new screen with just the Resolution field on it. Then attach that screen to the Transition to Done. 

Hi @Darren - Did you ever get this solved? 

You can have a single Default Screen - you just need to make sure the Resolution field is not on it anywhere. Either create a transition screen and add the field to it and then attach that screen to the transition to Done or simply set the Resolution in a post function on the transition to done. But it definitely should…

Also, if you are using Company-managed projects, you might try the Better Jira free Chrome Extension. It will let you set the width of the columns. https://chrome.google.com/webstore/detail/better-jira/adjlkmhgnjccbagimdppnminndehkmgl?hl=en

Hi Massimo - Welcome to the Atlassian Community! Thanks for the screenshots. The simple answer is that the board is designed to fill the screen. So a board with fewer columns will have those issues stretched to filling in the screen. 

Hey Sean - Welcome to the Atlassian Community! It definitely should NOT be setting the Resolution to Done on Create. Check the Create screen to see if the Resolution field is on it, and take it off. Are issues getting Cloned when the are created? Or some other method other than just the user clicking the Create button? 

Нажмите на значок шестеренки (Настройки) в правом верхнем углу. Если есть опция для управления пользователями, нажмите на нее. Затем найдите свое имя, чтобы увидеть, в каких группах вы состоите.

It might be under the Hide when Empty section of the screen. Click on the Configure link at the bottom right of the screen to move it up to the Context area. 

Hi @Tanguy Crusson - It's been a long time since we last talked. Is it possible to get some time with you about the Stakeholder Feedback module?

Eso podría ser el problema. Seguiría adelante y abriría un ticket de soporte con Atlassian para ver qué dicen. Publique la resolución aquí para futuros lectores. https://support.atlassian.com/contact/#/

There is a field called Organization. They should all have the same value and the users must all be in that same Organization. https://support.atlassian.com/jira-service-management-cloud/docs/group-customers-into-organizations/

So, this sounds like there is Issue Level Security applied to the project - can you confirm? 

Yeah, I really don't know of a way to do it. Seems to me there is a need for an app that can list issues seen by users in a particular time period. But I know of none that exist.

And the Organization value is on every ticket? And it is the same value on all of them? 

When you place/create an issue on the Roadmap, it might not be really getting created. Otherwise, since this is a Team-managed project and you have no control over filters for the board, it should show everything created on the project. After you create it on the Roadmap, can you go into a separate window and use the…

Hi Saqib, You can add a transition screen to the transition to Done and let the user select the Resolution. Or you can create create multiple transitions to the Done status and use a Condition on each transition for each Issue type. Then use a post function to set the Resolution field for each transition. 

Hi Rob, Under Jira Service Management, customers can only see issues that they submit or are associated with an organization they are a part of. Simply applying the Any logged in user would work only if all of the users have Jira licenses. 

Hi Lee, No, there is not restriction on the number of statuses that you can use in a workflow. However, you will see a performance hit at some point (dozens of statues). But saying that only 4 should be used and no more is simply ridiculous in my opinion. 

Hi Mariam, I can't tell you why the load happened on your system, but I don't think it's the automation rules or the post functions. It might be the complexity of the workflow itself in terms of the number of statuses/transitions or it could even be the number of custom fields you have created. Or something related to your…