John Funk Community Champion

@Whitni Smith - Any update?

You create a project with has all of the schemes/configuration that you desire. Then for any new projects that you create, you create them based on the existing project that you created with the set of of desired schemes. 

@Jenny Finneran - You don't need the 2 minutes to test. Once you have updated the rule, you can click the 3 dots to the right and select Run rule. It will run the rule immediately. But also, before then, simply run the query in the Filters/Search area to make sure something shows up first.

Hi Mustaqim, Have you checked the workflow to see if there is something there on the Create transition that would make it Required? Also, can you share a screenshot of what happens if you try to save the issue when creating and the error message it gives?

Same answer as above then. 

Hi Hafiz, What exactly are you trying to do? And can you share the rule that you have tried so far?

Yep, you can count me in as well. And FANTASTIC shirt!

Hi Kamil, Is this a Company-managed or Team-managed project? And, no, you can't rename a status to the same name as an existing status. You need to Copy the workflow you want to change. Then in the copy version of the workflow, you need to delete the current status and replace it with the other status. Then you need to…

So, what exactly is your use case/scenario that you are trying to achieve?

Hi Daniel - Welcome to the Atlassian Community! A project administrator might have turned that function off - you should check with them. Or check with others on the project to see if they can see the board. 

Hi Mujhahid, You would need an add-on called ScriptRunner Behaviours to be able to do that. And even thon it will depend on the types of fields you are using. 

Hi Jenna - Welcome to the Atlassian Community! The board shows the issues identified in the Board Filter. So just change the filter to shows the issues you want to see on this board. Create the new filter for the board. Be sure to share the filter with those persons who need to see the board. Click on the 3 dots in the…

Hi Fraser - Welcome to the Atlassian Community! The {{issue.key}} should be working with no problems. For the other field, try: {{issue.Employee Name_Starter.displayName}} The real question is, are there really any issues that are meeting the query. So, run the query separately in the search function to be sure there is an…

Hi Arlene, So is that working now? Also, you don't need the Re-fetch in this instance. 

Hi Julia - Welcome to the Atlassian Community! Can you share a screenshot of what you are seeing? Also, what type of project is this? Jira Software, Jira Work Management? Team-managed, Company-managed? 

Hi Dalhart - Welcome to the Atlassian Community! Unfortunately, the default values and description text for Jira Work Management projects will not work with the built-in simple form. If you have a Premium subscription for Jira you can add Advanced Forms which would allow you to have those. 

Hi Elina - Welcome to the Atlassian Community! I would strongly suggest that you create a Company-managed project. Then it really doesn't matter which template you choose because you can modify it to meet whatever need you have. 

I would love to have that conversation. Will you or someone from your team be at Team 24 next week? 

Hi @mbratu - Welcome to the Atlassian Community! Are your managed user accounts attached to an IAM tool that does the previsioning and deprovisioning? 

Hi Harish - Welcome to the Atlassian Community! You can create something like a service account user or test user per se, but that user needs to have a valid email address and someone needs access to the email address to receive it and accept the invite. 

Hi Misqah - Welcome to the Atlassian Community! Did you get this figured out? 

Hi Su - Welcome to the Atlassian Community! See the comments/updates in this: https://jira.atlassian.com/browse/JWMCLOUD-111

Hi Ben, What type of project is this? Jira Work Management? Jira Software? Jira Service Management? Team-managed? Company-managed? 

This will make the field required when a new issue is created, which does not seem to line up with the requirements in hi question. 

Hi Sunil, I am afraid there is not a lot you can do to prevent that other than adding the validator on each transition that would happen after that. Or you could create an automation rule that emails you when the field gets cleared after it has gone to through that status. Then you have have a little talk with them to…

Awesome! Glad you got that working!

Hi Jack, It still looks like there was another rule that ran at the same time since there is nothing in your rule that would cause it to be updated as Unassigned. You should be able to see the rules that ran against the issue to the bottom right under the Automation section. Click the Refresh to see what rules have run…

https://jira.atlassian.com/browse/JSWCLOUD-23094

Hi Jenny - Welcome to the Atlassian Community! Your CRON looks correct. Is it not running at that time? Or what is the problem?

Daffodils always remind me of Spring. When I see those starting to bloom, I know that winter will be coming to an end soon.