John Funk Community Champion

Thanks for posting those. Can you also post the Audit log for the rule that is generating the error? 

What type of project are you using? Jira Service Management? Jira Software? Team-managed? Company-managed? Jira Work Management? 

Hi Katelyn - Welcome to the Atlassian Community! If this is truly a Team-managed project, you just need to have Administrator Access to the project to be able to do the things you want to do. But be aware that the language you are using in quotes is more inline with Company-managed projects and not Team-managed projects. 

It sounds like Maria needs to be added to the Member project role. Give that a try and see if it helps. 

Sorry, but I am very confused as to what you are trying to do. Selecting a Quick Filter just narrows down the number of cards you see on a board. It has nothing to do with the creation of anything, if that is what you are trying to do. Just add the Epic Link field to the create screen so the person creating the issue can…

Great! I am glad that worked. That usually means that you have an extension running in Chrome that is interfering with it. 

Hi @Kateryna - Welcome to the Atlassian Community! Can you share a screenshot of your rule, along with the Audit log when you get the error? The error is going to be with the structure of your rule as it relates to a Condition, and not the code you list above. 

Fantastic! So glad you got it sorted out!

Hey @Amy Kehring - So sorry I never followed up on this. I must have missed the email somehow. :-( Did you ever get it figured out? 

Olá Administrativo - Bem-vindo à Comunidade Atlassian! Esta é realmente apenas uma mensagem de aviso e não uma mensagem de erro. Geralmente significa que o problema foi criado e colocado no status inicial do fluxo de trabalho. Às vezes, esse status não está diretamente no quadro, como no caso do status do Backlog.

It's a weird field to me - it is sort of text but not really because it becomes a list of values, also. But it's not a true list of values to me, either. But it is closer to that than text, which is what uses the ~

Alex went where I was going. If it is a Company-managed project, then you can create a Quick Filter for them if they are in the "tester" field. But it will not show their picture until it is actually assigned to them. 

Hi Johan - Welcome to the Atlassian Community! Is the person the Assignee as well as the "Tester"? Or does their name appear in a field other than Tester? Also, what type of project are you using? Team-managed? Company-managed? Jira Work Management? 

The JQL will be the same code in your Quick Filter.

Understood, but you’re not going to be able to do that. The user will have to do it his/her self.

Hi Etienne - Welcome to the Atlassian Community! The resolution field is probably on the create screen. Remove the resolution field from that screen, and you should probably be good.

Привет @Альмира Нет, вы не можете изменить дату создания задачи.

Hi Collin - Welcome to the Atlassian Community! Have you tried with a different browser? Or with Incognito mode? 

Hi James - Welcome to the Atlassian Community! So, this is not very straightforward, but I believe you might be able to get it accomplished with an Automation for Jira rule. Create a rule based on Issue Created trigger. Then add a Condition based on JQL and include the query from the Quick Filter. Then add a new action for…

Hi @Ivan Andrieiev - No, you are very limited in how you can interact with user's profiles. And you definitely cannot complete a new account for a user. 

Hi Ben - Welcome to the Atlassian Community! Yes, unfortunately, you have the best way to solve this because you cannot do a "move" using Automation.

Hi Nofar, No, it will not copy the automations from an existing project. But you can quickly and easily copy a rule and change out the project it is associated with. 

Hi Max, Yes, that's exactly it - Done issues disappear from the board after they have been marked Done for 2 weeks. 

Hi @RC - Did you ever get this solved?

Hi Inna, It says that you cleared out the issue security level for the issue. 

Thanks, Yuji! I have voted for it. 

Hi Catrine, They are only triggered on events caused by a user. You can create additional notifications for emails based on automation rules that can be scheduled, however. 

1. Don't do status meetings if you can derive the status through existing dashboards, Jira boards, etc. 2. Capture "parking lot" items for each meeting. This is for when an individual topic is getting too much attention and can't be solved in the meeting. Move it to the parking lot for another more focused group to engage…

@Dave Mathijs - That looks like my kind of candy!

Hi Parulian, You can use an automation rule to update the Approvers field with a person. But this should be done prior to it going to the status that has the approval attached to it. So in your case above, create a rule based on Issue Transitioned and then select the Change Request Management System status. Do a new action…