John Funk Community Champion

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

Great! Glad it is working for you now 

And what error are you getting when trying to apply the transitions to other statuses? 

I am not seeing the screenshots - can you repost? 

Is there another user that can tag you on a comment to see if you get an email from that? Just to see if it is limited to issue created or emails in general. 

Hi Erika, I do not know of a way to do this. The only thing that I can thing of is to create a tab on the Create screen in Jira called system or something like that. Then put those fields in this new tab so they are somewhat hidden. If you are really worried about them getting populated, then create an Automation rule that…

Unfortunately, I have been able to duplicate the problem. It fires, gives no error, says it worked, but it still doesn't have a value. :-(

Can you share a screenshot of the workflow? Core is very limited in what you can do with the board and workflow, but let's take a look. 

Hi Robert - Welcome to the Atlassian Community! Have you checked the Notifications Scheme to see who should be getting the emails when an issue is created? Also, check your Personal Settings (click on your avatar) to see if the box is check to You make changes to the issue.

Hi Kostiantyn - Welcome to the Atlassian Community! Can you share the Audit Log where it is not working? Are you sure you have an unreleased version on the project which has dates attached to it? 

In our setup, our repositories are all owned by the same organization. It is not an enterprise license, but a single Organization owns the repositories. Then we connecting Jira to GitHub, it connects to all of the repositories owned by that user/organization. 

Hi Fujiwara - Welcome to the Atlassian Community! Can you verify that you have created an unreleased version for that project? And does it have a date associated with it in the release? 

Hi Jeremy - According to your error, the Reporter field is not on the transition screen. Try adding that field to the Transition screen or whatever screen you are using when you cause the trigger to fire. 

Hello and Welcome, @DMC41155 ! We are glad you are here!!

Hi @l.rabino , What type of Project and Board are you using in your screenshot? What do the issues have in common in each swimlane that would allow you to write the JQL? In other words, what you want to see in each swimlane?

Hola Ignacio, Take a look at this article where it explains some about the difference in fields and update. https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/

Hi Norbin - Welcome to the Atlassian Community! Have you set up the initial installation at all? In other words, have you done this? https://support.atlassian.com/jira-core-cloud/docs/set-up-your-site/ Next, I would suggest following up with this:…

Hi Matthew, I am afraid you have run into a couple of bugs for sub-tasks with sprints in Next-gen projects. You can see those here: https://jira.atlassian.com/browse/JSWCLOUD-18461 https://jira.atlassian.com/browse/JSWCLOUD-18398 You might want to vote for those and start following them. 

I would try this: Go to Settings > Issues > Custom Fields For the first custom field, click on the 3 dots on the right side and select Context and default values Then in the URL, replace the custom field id with one from the error message - for example 10601. And then press enter. What field is showing up? And do you have…

Hi Aaron, We use a plugin called Calendar Sync for Jira which does provide feeds to Outlook. https://marketplace.atlassian.com/apps/1214714/calendar-sync-for-jira?hosting=cloud&tab=overview

Cool - glad you figured something out. I also failed to mention that you could probably just create an Automation For Jira rule and send your notification that way. 

Hi Vincent, Maybe try adding each Pod as a Component. Then change the Pod's board to only show cards where the Component = that Pod. That way you keep using the same card instead of cloning it. 

Hey @Dean Panos - Check the context foe each custom field to make sure they are available for the issue type and project you are using. Also, check the create screen to make sure those fields are available on the screen. 

Hey Douglas - Welcome to the Atlassian Community! I hear ya! I don't deal with server so it's a little more straight forward for me. But still the juggle of Premium versus Standard. Best I can tell you is to map out exactly what you want to get a price quote on as a start and work from there. 

Issue Moved would be a Move to another project - not a move to another status. Interesting that Issue Updated does not include the issue changing statuses. 

Hi Drake - Welcome to the Atlassian Community! Have you followed this guidance? https://www.atlassian.com/software/access/guide/elements/organizations-domain-claim#what-is-an-atlassian-organization

He Edwin, How are you placing a Notification on the Transition to the In Progress column? I see no functionality for that in the Notifications section. 

Hi Jan, You can copy Scheduled Trigger rules in Automation for Jira. 

I actually check for the full text - I approve this request and just the word approve. :-)