John Funk Community Champion

No, it wouldn't let you directly with a free account either. The goal is that Atlassian isn't flooded with the same problem with multiple people in the same organization/company. Let me see if someone from Atlassian can come take a look here. 

Hi Vinzenz - Welcome to the Atlassian Community! In the Permission Scheme, make sure that you have Browse Project and Create Issue permissions. Typically, the Administrators (or jira-administrators) group is either granted those permissions or the Project Role - Administrators is and that group is in that Project Role. 

Oh we're gonna go there are we??? HAHA. I guess it would be baseball for me. I played one year when I was 7 years old. But we were terrible and lost pretty much every game. Our coach even rarely showed up! So that was enough for me. I did enjoy playing softball once I turned 16 and played for several years. And, I don't…

Hi Sama, Not that I am aware of. But it will be well worth your money in my opinion. :-)

Hello and Welcome, Odilbek! We are glad you are here!!

Hi @Ruchi_Uppal - Did you ever get this solved?

Hi Sharee - Welcome to the Atlassian Community! What type of project are you using? Team-managed? Company-managed? Jira Work Management? 

Hi Foliant, What type of project is it? Team-managed? Company-managed? Jira Work Management? If Company-managed, you should be able to do that by changing the Field Configuration for that field for that project. 

Thanks for adding more information. Can you share a screenshot of one of the issues? It would need to be a full screen. And are you using the standard Labels system field? Or did you create a new custom type Labels field? 

Sorry, I was referencing a free trial of the paid version. 

Hi Aditya - Welcome to the Atlassian Community! If you are asking about creating automation rules specifically, here is some information to get you started. There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month * Project: In all versions, you get unlimited…

This applies if you have a Free account in one instance, or if you have a paid account and you are not a Jira Administrator for your instance. Are you not able to get your Jira Admin to submit the bug? Or are you on a free account? 

Hello and Welcome, Dele! We are glad you are here!!

Hi Francisco - Welcome to that Atlassian Community! After the issue has been done for 2 weeks, it automatically drops off of the board. This is built-in functionality that cannot be changed currently. 

It's probably part of the paid version then. :-( You can do a free trial and see if that works for you. 

Hi Paul - Welcome to the Atlassian Community! You will nee to contact Atlassian Support directly: https://support.atlassian.com/contact/#/

Looks like loads of fun!!

Dang - I'm worn out just reading that. :-) Thanks for all of the hard work, Bill!

Hi Murray, You can submit bugs and requests here: https://support.atlassian.com/contact/#/

Great article! Thanks for sharing!!

That's probably a question for Atlassian Support. 

Hi Dylan - Welcome to the Atlassian Community! What type of project are you using? Company-managed? Team-managed? Jira Work Management?

Can you post your new rule?

@Benjamin Peikes - Any update here?

My example above was just using made up numbers for the custom field IDs. Did you look up the actual IDs for the fields you wanted to use? 

Okay, go back to the triggerissue then and see if that solves it. 

Hi Bogdan - Welcome to the Atlassian Community! This might be a cache issue. I would try using a different browser or open a browser window with Incognito mode and see if it is there there. 

HI Wajahath - Welcome to the Atlassian Community! You can do that with an Automation for Jira rule. Create a rule with a Field Value Changed trigger. Then select the custom field. Then add a Condition for Issue Fields Condition and put in the value for the custom field. Then add a new action for Edit Issue. Select the…

Hi @Mumin Salimov - Did Andy's response answer your question? 

No, try {{issue.initiator.acctID}} in the log function to see if that brings something back.