John Funk Community Champion

Hi Jennifer - Welcome to the Atlassian Community! You should be able to add something to the effect of initiator != assignee

Proud to call so many Atlassian Champions friend!!

Great! Glad to hear and you are very welcome. 

Hi @jodi_klein - I guess you have already realized that you cannot change the type of fields and that you would have to create a new custom field. Regardless, did you get this sorted?

Hi Wessel - Welcome to the Atlassian Community! My recommendation is always to switch to a Company-managed project. If you want to try the second board first, here is an article to help guide you through that. Give i a Like if it is helpful for you please.…

Great to see so many new names!!

Woohooo!! This is awesome!! Thanks @Yukti Tuli !!

Yep, Bill is the GOAT of Jira Automation

Hi Elvira - Welcome to the Atlassian Community! Just open a different browser type (if using Edge, then open Chrome or vice versa) or open an Incognito session with your browser. 

We'll get someone from Atlassian to come take a look for you. 

Great to hear! And you are welcome

Hi Maksym, As far as I know, there is no way to turn this off for individual fields. It is all or nothing. 

Hi Bud, You should be able to find lots of examples of this in the Community. Here is one: https://community.atlassian.com/forums/Automation-questions/Sum-up-Story-Points-from-Stories-Under-Epic-Jira-automation/qaq-p/2674049

Hi Adam - It should include all of those when it exports. However, any keys will not match up with the keys in your instance. You just then need to do a little clean up to select the right values for those things. 

Figured as much. And understood on the duplication. Where the portfolioChildIssues functionality comes in handy is when you are searching for children of issue types higher than Epics in your issue type hierarchy. Sorry the other didn't work, would be nice. 

Hi Mertcan - Welcome to the Atlassian Community! Labels are globally available in Jira. Just because you might not be using that label, if you delete it, it will delete it in the entire system, including for others who are using it. I suggest you start using Components instead of labels. Then those will be just for your…

Hi Mike - Welcome to the Atlassian Community! You have probably already seen this page with instructions: https://support.atlassian.com/confluence-cloud/docs/configuring-an-admin-announcement-banner/ But I don't think Announcement banners are available for Free accounts/subscriptions which you indicate you are using. There…

You are welcome - thanks for asking questions! I don't think there are any alternatives - even Tempo Timesheets though they store the data in there own database, sync with the Timespent field. Also any native Jira reports using time would be based on that field. Other marketplace apps (basically competitors to Tempo, use…

Hi Vladimir - Welcome to the Atlassian Community! You should definitely check out Atlassian Statuspage: https://www.atlassian.com/software/statuspage/features Also, with Jira Service Management, you get alerting and other similar functions. 

Hi Leo - Welcome to the Atlassian Community! If the new navigation is just now showing up in your organization, I would say give it a couple of days to finish out. If there are still problems, then open a support ticket with Atlassian. https://support.atlassian.com/contact/#/

Hi Charles - Welcome to the Atlassian Community! Try this: issuekey in portfolioChildIssuesOf("ABC-123") to see if that is pulling back what you want for that Epic. (Where ABC-123 is an Epic). I don't think you can put filter = 1234 in there instead, but give it a try. Otherwise, try multiple epic keys separated by a…

Hi David - Welcome to the Atlassian Community! Yes, you can do it in Cloud. See if there is a + button underneath the Summary/Title on the left side. If so, click on it - the Link issues function might be a little hidden. If you still can't find it, please post a screenshot of what you see on the issue screen. 

Hi Tyler - Welcome to the Atlassian Community! Can you share a screenshot of what you are seeing?

I think what I would do is create it as a Manual trigger and have your team members execute the trigger on the comments they want to, which would copy up to the parent issue into the desired Field, adding to the values already there. 

So step 2 says: * It migrates the item from IHD to DH You can't use automation to "migrate" an issue. So based on your rule so far, it looks like you are creating a second issue in the other project (Development Hub). So far so good. In the creation of the Story, add the Linked Issues field and select to link it to the…

Hi Alhyatt - Welcome to the Atlassian Community! I don't see who it could unless some type of license free account is setup like customers for JSM. We'll have to wait and see!

Hi Stephen, I would add a Branch for Linked Issues and move those other actions under it. You will need to change the Link Issue action to be based on Trigger issue instead of Most recently created issue. 

Okay, thought so. Change it to Multiproject and include both the current project and the project for the story (Development Hub) and then run it again and see what happens. 

But is the rule a multi project rule in the rule details, with both projects selected? Or is it a single project rule? 

Looking forward to this webinar and seeing what Loom AI can do!!