John Funk Community Champion

Hi @Paisley - maybe check the box that allows other rules to execute it - just as a test. Whenever something doesn't fire for me, it is usually one of two things - it's on a different project as Jack says. Or another rule is firing first. 

For me, it's about seeing people face-to-face. When you are both in the office together, spend time together - either over lunch or take a walk, etc. If out of the office, then use video to share things about your life that is going on - not just face time, which is important, but show some things around your home, like…

Nic probably used all of his up in his smoothie anyway. ;-)

Hi Kazumi - What are the statuses of the cards that are not showing on the board? Are they in a Done status? 

Can't go wrong with pizza!! You should put some pineapple on there for @Nic Brough -Adaptavist- 

Hi Asparuh, When you grant a user browse project permissions, it gives them access to the issues within the project. So you can't grant a user permissions to see some information about the project without granting them access to the issues themselves with out of the box Jira There are some third party options for…

Hi Peter - Welcome to the Atlassian Community! Forms are associated with issues. So you can use the form to create an issue that will then show up on your board. So, forms are used to create issues, and boards are used to display the issues in an easy to see visual format. 

Great! Glad that helped. 

Hi Noura - Welcome to the Atlassian Community! There is no way to change the project type after you create a project. You would need to create a new project with the desired type and then Move (migrate) the existing issues to the new project using the bulk change function. 

Like I mentioned above, there is no way to do that in the same instance as when you click on the checkbox. The fields could only become mandatory when you tried to move the issue to the next status in your workflow. 

I love the blueberries on top for that extra touch!

Hey Andrew - Welcome to the Atlassian Community! The only think I can of is to add a transition screen to the Create transition that asks if everything is ready for create (or something to that effect) and add a Yes/No custom field. Then add a validator to the same transition that checks to make sure that the custom field…

Hi Jasmin, Currently there is no way to control this with JWM project boards. Eventually, the cards will disappear from the Done column - I just don't remember if it is after 1 week or 2 weeks. Hopefully, they will be adding the ability to hide Done cards using the quick filter on the board - but not sure of a timeline for…

Picked up eating more than I should. Okay, maybe that wasn't completely new, but I have perfected it. And unfortunately, it has stuck - literally!

Awesome - and fantastic progress!

You are welcome!

Hi Bill - Welcome to the Atlassian Community! Yes, the filters and dashboards will still work, but you really need to change the ownership. So, yes, you can change the ownership, but you must be a Jira Administrator. Go to Settings > System > Shared Filters (or Shared Dashboards) Search for the filter or dashboard in…

Yes. 

You can use the Field Required Validator or add a condition for Value Field - then enter the field name and use != for the condition and leave the value field blank (empty). Using a Condition will not show the transition at all if the field is not populated. You probably don't want that. With a Validator, you can add a…

Okay, let me see if someone with Atlassian can join here. 

Hi Mohan - Welcome to the Atlassian Community! Those buttons are simply the transitions that are available. So to remove the button, you would have to remove the transition. 

Hi @Vaishnavi Muchi - You cannot do that during the creation of an issue with Jira Cloud. You can create the issue and then prevent the transition to other statuses using a validator or condition, but you can't make other fields mandatory in the same step as you click the check box. 

Hi @Social Streets C.I.C - Welcome to the Atlassian Community! You should contact Atlassian Support - sometimes emails get blacklisted and you would need to get them to release it. https://support.atlassian.com/contact/#/

Hi Peter, Simply write a JQL filter like: reporter = username and statuscategory != Done That will show you all of the open issues where that person is the reporter. For the username you can use the actual username, but you will need to type it in if their account is already disable. Or you can use the account ID. Once you…

Yep, that’s the right path

I still don't understand how you would know which task is going to which developer next. There has to be some type of logic there.

Hey Matt, You probably need to create a series of IF/ELSE logics with the email created each time with different email list. You can't copy the send email object in automation, but you can copy and past the email test which should make that go quicker. 

Hi Orry, I am not sure if it is the same with Server version or not, but in Cloud it depends on the project used in the Location field for the board. so both boards would need to have the same project.

Hi Priyanka, If this is a business project, yes, it should behave as you describe above. The simplest thing to tell is to try it out. :-)

Yes, that is correct, sorry. @Natalie Franklin