John Funk Community Champion

I guess that is what you were trying to do with above. :-) That's outside of my expertise, but you definitely should be able to accomplish it with the tool. 

@Sanket Parlikar {Revyz} 

You mean don't run the query on the weekend? What's your CRON look like? You can get help here: https://crontab.cronhub.io/ Or this one is even better: https://freeformatter.com/cron-expression-generator-quartz.html

Oh, are you in Server or Data Center? Also, there should be a free Lite version of Automation for Jira that you could use. Do you have ScriptRunner or some other plugin for workflows? 

So I would create a filter that just uses the Team and the new project and see if issues come up. If so, I would update the filter to take out the new project and see if the issues show up again. 

Não, estou perguntando que tipo de projeto é - gerenciado pela empresa ou gerenciado por equipe.

É difícil dizer porque não sei o que o outro sistema faz ou como preenche seus campos internos a partir do email que recebe.

Hi Helena - Welcome to the Atlassian Community! If either project is a Team-managed project, then the answer is no. If both projects are Company-managed projects, then the answer is yes, as long as you have the appropriate permissions for each project. 

Great! Glad you found that. 

Hi Sia - Welcome to the Atlassian Community! You have the fields for the Bug being copied from the Current Issue. The Bug is the current issue, so there are no values for any of those fields. You need to copy each field from the Trigger Issue instead. 

You don't need all of that. Just create an automation rule that is based on an Issue Created trigger. Then add a Condition for Issue Type = Snow-bug Then add an action for Edit Issue. Select the Parent field Put in the value GOXFUNC-8734 Update the issue and you are good to go. 

It maybe not be a biggie to you, but I don't think it is available to you in an easy manner. You come to the board at 1:30 pm. And then the board stays open for 3 days in your browser. What value is it going to use? 

Hi Suma If you added the post function to set the Resolution for all workflows for all issue types (as you should), it will not automatically update all of the existing issues. You could try to export those issues into a CSV file, add a column for the Resolved Date and populate that column with a value for each issue. Then…

Hi Preeti, Are you saying create an Epic every time an issue is created with a certain issue type? Or link it to an existing Epic? And if an existing Epic, then how will it know which one? 

Hi @albinbrengesjo It's not going to know when is the last time you visited the board. If it is a Company-managed project, you could add a Quick Filter for issues update in the last day or something like that. 

Hi Volodymyr If the email addresses no longer receive any Atlassian/Jira emails, there is a good chance they ended up on an email Suppression list with Atlassian. You should open a support ticket with Atlassian to have them test it. https://support.atlassian.com/contact/#/

Hi @integrity-jira-user That's not possible to have different workflows for the same issue type (Epic in this case). You could add the new statuses to the existing workflow and add a Condition for the transition to each status that the Created field (date) must be >= 2024-04-16 or whenever you implement it. But it would…

Hi Peter, I don't know of any way to do that with the current product. You should open a support ticket with Atlassian to double check and if not there, they can open a Feature request for you. https://support.atlassian.com/contact/#/

Hi Jonathan - Welcome to that Atlassian Community! Have you tried with different browsers to see if it is there in all of them? Also, what type of project is this? Jira Software? Jira Work Management? Is it Team-managed? Company-managed? 

Be sure to run the query to test it to make sure it does what you want.

Oh, sorry about that. Try changing that to BEFORE -24h or even -23h

Hi Shery - Welcome to the Atlassian Community! You can use something like this: assignee was john.funk on 2024-04-01 That would show everything for which I was the Assignee on April 1, 2024. You can replace the date with the date of the start of the Sprint. Also, when you are typing this out, you should be able to start…

Hi Colton - Welcome to the Atlassian Community! In the future, it is best to create a new question in the Community so more people will see it. :-) Same questions for you as for Oliver above - what type of project is it? I would actually use Components to separate your work in to "categories". 

Hi @정영환 If I am understanding you correctly, you could do that with an Automation Rule. It would be something like in my example below. Try it out with the JQL in the Scheduled trigger to be just one issue key, to make sure it works as planned. Then you can do a broader JQL. After you get everything done and click on the…

Hi Simon, Custom fields will not be impacted. Just check to see if any of them have a context that is only attached to JSM projects. They will still be available for Jira Software. If you have any automation rules that connect JSM projects to Jira Software projects, you would want to disable them. 

Hi Niki, You can use shared fields now, you just have to initiate them like you would with a Company-managed project. You go to Settings > Issues > Custom Fields and create your custom field. Then add a context for it for each project that will be using the field, regardless of the project type. Then when you are in the…

Good to hear!

Hi Jessica, The Queues in Jira Service Management are designed for that. Granted, they do not have inline editing like in Jira Work Management, but they should show you want you identify in your question. 

Hi @integrity-jira-user - You can create a new issue type for Bug as a Sub-task issue type. Then your hierarchy would be Epic > Story > Bug (Sub-task)

Hi Irfan - Welcome to the Atlassian Community! You can find more information here: https://www.atlassian.com/partners/join What part of the world are you in?