John Funk Community Champion

Absolutely NO! If if the system allowed you to do it somehow it would be disastrous internally to the system. 

If you type the username of the deactivated user it will still work. Let's say Mary Jones becomes deactivated and her email was mary.jones@abc.com Her name will not come up when you start typing Mary but if you type in the full name such as reporter = mary.jones then it will find the issues where she is the reporter. 

Hi Munir - Can you be more specific on exactly what you fields you are wanting to copy over? Also, is there any connection between the two Epics other than the Epic Name is the same? 

Personally, not buying into any definition of a sandwich that involves a bun or a tortilla, :-)

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

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

Hi Munir, You need to make sure that the fields are available for the new project and that they are on the Create screen used by the new project. What type of project is this? If Company-based or JWM/Business projects, then you need to go to Settings > Issues > Custom fields and check the context for each of the fields. It…

So far so good - just make sure you get the right ID for each of your custom fields and that they are in the right order in your formula

Have you put in a support ticket with Atlassian? https://support.atlassian.com/contact/#/

Awesome - that's great!

Hi Maciej, I would create an automation rule based on Issue Created trigger. Then create a series of If / else block condition where it looks something like: Use Issue Fields condition for the IF If component = Blue Then new action for Clone Issue with issue type of Sub-task It would look like this:

Well, my suggestion would be that you link the tickets in someway when you create the second one. That way you have the ability to send notifications to people associated with the original card when something happens with the second card. 

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

But I have to admit, if I am getting ice cream from a truck in the US it would be an ice cream sandwich as well. :-)

Hell and Welcome @vemanivenkatesh ! We are glad you are here!!

You will probably find that no matter which To Do status you use, it will probably work. 

Hi Amanda, I would do a filter such as key in (ABC-123, ABC-456) and "Epic Link" in (ABC-123, ABC-456) That will move those two epics and all of the issues in those epics. Do that as many times are you need to until all of your issues left are under 1,000

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

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

Hi Jacki, This applies to Jira Work Management/Business projects only. You should have it for those by now. 

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

Hi Jason - Welcome to the Atlassian Community! Take a look at the filter for the board to see if it changed. Got to Board Settings > General And look at the Filter query

Just update exactly what you have already except change out > startOfDay() with < now()

Ah, now that I think about it, I believe it is your query. try doing the Planned end date as < now()

I don't know why the Dashboard is different than a regular filter query but I suspect that only the single shared status value of To Do shows up there - unless you include the project value of the Team-managed project. 

Hi Naomi - Welcome to the Atlassian Community! They may already have that on their list, but I would drop a note with that suggestion at this email address: jwm-eap@atlassian.com

Here's a feature request you can vote for and follow to be able to set the default for the way you want it. https://jira.atlassian.com/browse/JSWCLOUD-21494

I still think it is a permission thing with how you are using the webhook - can you share the webhook you are using? 

If you hover over the value, you should see a popup that shows that you can display the link.

Hi @kheckaman1 - Welcome! You can use a filter like: Project = ABC and statusCategory != Done This will get you all issues that are not Done (i.e. open).