John Funk Community Champion

Hi James, Inside the Clone issue action, click the Choose Fields to Set dropdown and select the Component field. Then you can set a value for it. 

Hi Florence, No, I don't think it is a phishing attempt. I got the same email and it matches all of the other emails I get from Atlassian. 

Good call

Hi Bejamin - I suspect you are right. @Simmo - Can you verify? 

Hi Arthur - Welcome to the Atlassian Community! No, that is not possible and you should not try to do that. In our organization, the project is really more a Team and not a true project, as it will never really end for the most part. So, it's just an education on our part that when you see Project, think of a Team. 

Hi Steve, No, you can't trigger it when just viewed - nor do I think that you really want that. You can create a manual trigger that when you go to the issue, you can trigger it by clicking on the rule execution then. Is that what you are looking for?

Hi Craig - Welcome to the Atlassian Community! Maybe try: Project = ABC and updatedDate <= startOfDay(-3) and status = "In Progress" Obviously, you would want to change the status value to whatever value you use in your workflow, and same with Project. 

Hi @niggles20 , Maybe try {{issue.resolution.value}}

Hi Cristian, When does it not work? What are the steps you are doing? You said it works but you can't get it to work, so I am a little confused. 

You are very welcome. 

Hi Holly, For multi-line/paragraph fields you can change the rendering of the field in the Field Configuration scheme for that project to use Wiki-style rendering. 

Great - glad that worked for you. For other people, you will nee to use the watcher = username (or email or acct id)

Hi @Foxcliffe Hickory - Team-managed projects use a different process for Epics than the standard Epic Link field used for Company-managed projects. You will have to do the linkage directly inside your project. 

Hi Michael, Why don't you just use the Watched Issue gadget in a dashboard? You should already have that gadget in your System Dashboard if you want to look at that first.

Hi Daria, You can use the Link Issue function to link any two issues in the system. They don't have to be on the same project. 

Hi Pramod, You can do this a few way - using a post function on the workflow or using an add-on like Automation for Jira or ScriptRunner.

Hi Cristina - did this answer your question?

Hi Hagen, It looks like someone has deleted that filter. 

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

Hi Jacob, You can create a Scheduled trigger in Automation for Jira to do that. 

Hi Camilla - Welcome to the Atlassian Community! Go to Settings > Issues > Issue types and create a new issue type. 

I know this is very basic, but it was a great day when I figured out that you could have separate Create, Edit, and View screens then then take fields out of the Edit screen so they couldn't be updated. :-)

Hi Phil, Not sure if this is where you are going or not, but you can create a custom field for Insight Object type. The insert the field into one of your Jira screens. This will pull values from an object in Insight. 

Hi Steve, You can use Automation for Jira to do that. You could base it on one of the first two fields being updated, the update the Total Story Points field based on a formula like: {{#=}}{{issue.customfield_16719}}+{{issue.customfield_16939}}{{/}} Using the custom field id for Story Points and QA Story Points. Or it…

Hi Prabhu, How many options are in the single select? You can always remove the single select field from the create screen. 

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

Hi Lars - Welcome to the Atlassian Community! I think someone with Project Administrator permissions should be able to create the form on the project. 

Hi Roja, Try creating a filter that shows all of the tickets you have resolved. Then run the Created vs. Resolved Issues Report for a project but switch out the filter that is used for your new filter. 

Hi Endy, Not sure why it would do that other than the time is off somehow. Have you considered running it later in the morning - maybe 3:00 am? And then see if the results are different. Is there a reason it needs to run at 1:00? 

Actually, I am pretty sure that if the component exists by the exact same name between the projects in Cloud, then the value of the component field will be retained in the move.