John Funk Community Champion

Hi Murad - Welcome to the Atlassian Community! If you have either a Team-managed project or Jira Work Management project, you will not be able to alter the 2 week period. 

Hi Craig - Welcome to the Atlassian Community! Try using this: project = CP2 AND issuetype = Bug AND status in ("In Analysis", "In Development", "In Test", "New Ticket", Reopened) AND (Component not in ("Reporting") or component is EMPTY) ORDER BY created DESC

Hi Gregory, To change the description, you will need to edit the Field Configuration for that project. 

You cannot alter the board in Jira Work Management projects - there is no Board Settings

Hi Sherryl, You might try this in the very last slot: 5#1,5#3

Hi Jewgenij - Welcome to the Atlassian Community! Unfortuantely, that's all you can control right now. I think th Atlassian developers have plans to add custom fields later, but I don't know a timeline. 

Hi Volkan, For issues to be considered complete in a sprint, they must be in the last column of your scrum board, regardless of the status. For your screen shot above, please move the Done column to be the last column (to the far right) on your board. 

Great! Thanks for testing all of that out - good info!

I would go ahead and submit a support request to Atlassian: https://support.atlassian.com/contact/#/ Please post back here with the solution so we can close it out. 

You would need to ba a Jira Administrator to make the changes. 

I hope it works for you. 

@Alex Shirokov - this a duplicate post of this one? https://community.atlassian.com/t5/Jira-Software-questions/Take-value-of-one-custom-field-in-Issue-1-and-place-it-to-the/qaq-p/1919811 There is no need to post a question twice on the Community. Please see my answer on the other post. 

So you got the same error when you did a bulk change for the edit??

Hi @Ruslan Rekk (Ploskonos) - Did you ever get this worked out?

Hi Alex, I would use a Component to designate which Epic is the top level Epic. Then create an automation rule for Issue Created with a Condition for Issue Type = Epic You will need to create a Branch to identify the top level Epic (using the issue type and component combination)

Love it

Hi Alex - Welcome to the Atlassian Community! You can do exactly what you describe by putting the custom fields at the Epic, and then copy the values down from the main Epic to all other Epics created on that project. I would simply add a component such as Top Level or something like that so you know which is the Top Level…

Hi @Praveen Rana - Did you ever get this working?

Can you share the rule? Make sure the rule has the box checked on the Details page to Allow rule trigger. 

How can you not love this Joey look:

Hi Paulo - Welcome to the Atlassian Community! Make sure that the context for the field includes the new project. 

You have to remove the Project from the Contexts and make it global except for the issue types. 

You are welcome. :-)

Hi Seetham, Try this for the update to the custom field: https://abc.net/browse/{{issue.Cloned By}}

Oh, for that I would save your filter above. Then create a Dashboard with a gadget for Issue Statistics. Use the QA Tester field for your Issue Statisic. This will group by the name and give you a count by user. This assumes the field is a user picker custom field and not a text field. 

Just don an Order by on that field and it will group all the testers by name. PROJECT = Ecommerce AND (STATUS WAS "QA Testing" AFTER "2019/08/15") AND (STATUS WAS "QA Testing" BEFORE "2022/11/20") ORDER by "QA Tester" Or whatever the actual field name is where you are storing the tester's name. 

@Matthew Knatz - You should probably do that. And put in a much detail as you can about what you are trying to do. :-)

Hi Jose, You could set a custom field value (we created a custom field called Generic Yes Field) when you send the email and then create your rule based on a Field value change trigger. 

Hi Danny - Welcome to the Atlassian Community! Yes, you can do that with automation. Create an Automation Rule based on an Issue Created trigger. Then select new action and choose Edit issue For the Summary field, type something like this: {{issue.Third Party}} - {{issue.Provider}}: {{issue.Ref No}} - {{issue.Brief Desc}}…

You are not able to have two different contexts by project - only by issue type.