Jack Brickey Expert

@Jogchem Andre Oord , at this time that is correct. Parent replaced epic name a few months back. At the time this post originated however, that was not the case.

I will see if I can get someone from Atlassian to chime in. There could be better info out there.

Hi @Suman Modi , welcome to the community. It is important to understand that this community forum is a public forum and as such generally not a good idea to share your email address or other personal information. Now to your question, assuming you have administration access you can downgrade this yourself by simply…

Hi @Eran Roiter , you would need to have some custom field or label indicating a FD ticket. In the past when I incorporated fresh desk into my Jira projects, I would include a fresh desk link. I'm unsure if whoever set this up, included such information in your instance.

Hi @stephanie nacion , I expect we can get you to your requirements. However, I am unclear about the last part - "an annual review will trigger", can you elaborate on your use case? you can certainly schedule a rule to run annually and you an certainly send various notifications when an issue transitions into any status,…

Hi @john terebey , what do you mean by two column editing?

Example rule output looks like... Time was 848 days 0 hours 11 minutes 31 seconds

Hi @Vera Valshonok , if you mean you would like to display the time between Created and Resolved for each issue then I would suggest adding a custom field (e,g. Time open, etc) and use automation to populate that field when an issue is resolved. the following Automation smart value should give you the time in hours,…

Hi @iain mackenzie , not sure I follow. The column heading in Queues is the field name and you cannot change that behavior.

Hi @EnEm , fair question and unfortunately difficult to answer I am not immediately aware of any definitive roadmap. You can monitor "what's changed" by clicking the "?" In-app but that is after the fact. My expectations are that we will continue to see a convergence of features as updates are released, especially where…

Hi @Mina Rose Guevarra , you might want to reach out to the vendor support directly. You can find a link to their support via the marketplace for their app.

Hi @aaron_simon , welcome to the Community. Archiving more or less just hides a project. So whatever issues existed in the project at the time of archiving will exist when restored nothing more nothing less.

Hi @Charles Kato , please make sure the "Epic Status" = Done not the issue Status. I realize that may be confusing but there are two status for Epics. The Epic status is what governs whether the epic appears in the backlog.

Hi @Suman Chakraborty , The default system Description cannot be bulk edited - JRACLOUD-81821. I am thinking that someone has created three custom fields called "Description". You can confirm this by going to admin > issues > custom fields. I expect your actions edited those custom fields.

Hi @Suman Chakraborty , what screen are you doing this from? Maybe screenshots would help us assist more quickly.

Is this a company or team managed project? Is this a software or work management project? When you say the are automatically sorted can you interpret the "sort by" results?

Unsure what may be the cause. I would follow the recommendation in the error message and open a ticket. If you do so and hear back please update us here.

Hi @Yi Liang , welcome to the community. Unfortunately, JQL does not allow you to compare dates. One option you could consider would be to use automation a company with a custom field. The concept is to set the custom field if the resolved date is greater than the required date. Automation allows for this comparison. Then…

I would try to first clear the CRT then change the Issue type then set the CRT. You may have to use the move operation when changing the issue type. I have not tried in awhile.

Ok. I suspect the name may be taken or is otherwise not allowed. Try a different name.

Ugh! Yes indeed, how sloppy of me! 😣

you might have a look at this in case it sparks ideas for you - Automating-tickets-for-future-not-next-sprint . The idea is to copy from another issue that have the desired future sprint.

@Olivier Mulot , I am wondering how your rule would know what sprint to assign the issue to. Certainly the rule would not use a static sprint name. Just a bit confused on the use case.

Hi @Sjoerd Hemels , welcome to the community. Could you try adding a branch for issues in sprint first? See below for example.

Please share your automation rule. I think the way I would approach is to clear the Customer Request Type (CRT) first, then change the issue type, finally set the CRT.

No clue. Where are you receiving this error code and what were you doing when you received it?

Unfortunately not. You would be better served with addon apps or consider exporting and using excel/sheets.

Also check if anyone can access the project. If no one can, then it likely has been deleted assuming it ever existed. If others can't access that it is a permissions issue and you will need to talk to a project/site/org administrator to give you access.

Is it possible that the project was deleted? Check by clicking on the cog in upper right and choose Projects. Look in Trash and Archive in the sidebar. if you cannot access this area, then you will need to contact your organization administrator.

Hi @Vidya VASUDEVAN , this seems pretty straightforward. I would creat a copy of the current workflow and edit the copy per the details you provided. To copy/edit a workflow in company managed projects: * project settings > workflows * copy the workflow * find the new workflow in the Inactive workflow area - admin settings…