Petter Gonçalves Atlassian Team

Hello Craig, As mentioned in my last message, I've found another option to achieve this matter, better than the one sent before. I realize that the automation I mentioned in my first answer is not required to achieve the functionality you are looking for. That been said, please let me know if the steps I provided in my…

Hello Vladimir, Thank you very much for your reply. Indeed, I was trying to reproduce your problem unsuccessfully, since I was not aware of any add-on that could cause this behavior. Have a nice day!

Hello Dave, Thank you for your feedback regarding the new issue view and Next-gen projects. Indeed, you are correct to say that sub-tasks are not available for Next-Gen projects yet. We also have a feature request opened to implement it here: - No option to add a issue type "sub-task" for next-gen projects Regarding the…

Hello Anil, As @Joe Pitt mentioned, it's not possible to change the Resolved date field. The best option to keep it would be by re-importing the issues with the correct Resolved date without changing its resolution. Here are steps: - Export the current Resolved date of your issues to a CSV. Let's call it resolved_date CSV…

Hello Pooja, Unfortunately, I'm not aware of any way to extract the worklog by status on JIRA, however, you can have this information using the report Pivot By Status provided by the plugin Time Reports: Please, let me know if that's the functionality you are looking for.

Hello Netta, Welcome to Atlassian Community! As you may know, the new issue view is still a lab feature on JIRA, so our developers are still working to implement some features to it, including the permalink on comments. That been said, we have created a feature request to better track their progress: - Ability to link to a…

Hello Stephen, Unfortunately, JIRA understands that a new mapping of Fields, screens, and statuses is required when you change the issue type to another one which is using a different workflow. That being said, the only way to change the issue type in a simple field selection would be by setting all your issue types with…

Hey Craig, I used the Due date field to trigger the automation. In fact, you can use any date field to do it, I've only suggested a new date custom field to avoid confusion with your users since this field will be used only to trigger the automation and nothing else. In fact, I've found a better option to achieve this…

Hello Rui, Welcome to Atlassian Community! You can use the plugin Automation for JIRA to achieve this goal. You just need to create the following rule: Of course, you will need to create an action to create each issue for your users. Please, let me know if it works for you.

Hello Chris, Thank you for your feedback. Actually, this is a strange behavior that I was not able to reproduce from our side. As you can see in the screenshot below, it is displaying just like I type it in the ticket description: That been said, could you please provide a video or the screenshot displaying how you are…

Hello Mark, Welcome to the Atlassian Community! As you may know, the new issue view is still a lab feature on JIRA, so our developers are still working to implement some features to it, including the Watcher's list and the ability to add other users as watchers. That been said, we have created a new feature request so they…

Hello Craig, Thank you for raising this question. After trying some options using Automation for JIRA, I was able to achieve the functionality you were looking for by performing the following steps/requirements: - Create a date custom field and add it to your project screens - When starting the progress on The sub-task 4,…

Hello George, Thank you for raising this question. About the first problem you mentioned, can you please let us know where is the place that you do not seem your Custom priority Icon? Is this in the issue navigator o in the issue detail view itself? Let me know if you are being impacted by the following bug: - Custom icons…

Hello Tina, Welcome to Atlassian Community! Indeed, you are correct to say that the new issue view description is not able to render Icons, so we reported it as a bug to our development team: - Issue detail view: unable to add icons to "Description" field Please, feel free to become a watcher to be aware of any updates…

Hello, Gikku. Indeed, I think this Custom field type will not be implemented anytime soon as it can be done with a simple text field. However, feel free to open a feature request on JAC if you think this field may be required in the future for your business: - https://jira.atlassian.com Have a nice week, Gikku!

You are welcome, Jennifer! Have a nice week.

Sure, Jennifer! You will find the option mentioned in that documentation by performing the steps below: - Navigate to Issues and Features > Search Issues - Click on the three dots Icon at the application header > Import issues from CSV: Please, let me know if that option appears for you.

Hello Nicolas, welcome to Atlassian community! The next-gen projects is still a lab-feature on JIRA that was implemented for those customers who wish a more practical way to manage their tasks, simpler than the Classic Scrum and Kanban projects. That being said, our developers are still collecting customers feedback to…

You are welcome, Chandrasekhar. Have a nice weekend!

Hello Senthilkumar, Thank you for your feedback about this behavior. Performing some tests on my side, I could reproduce your issues when adding the special character & to the workflow's name. When removing this character from the name, the problem does not happen. That being said, I have reported this behavior as a bug to…

Hello Chandrasekhar, Welcome to the Atlassian Community! I believe you are probably facing a cache problem in your Browser. Please, perform the following steps to confirm it: 1 - Try to clear your browser's cache and restart it 2 - Try a different browser and let us know which ones you have tried 3 - Try to access the same…

Hello Yashveer, You can create the following filter to achieve your need: (issuetype = story AND status not in (Canceled, "which are released")) or (issuetype = Epic AND status not in (completed, cancelled, implemented)) The brackets added to which query should properly separate and execute it. Let me know if the query…

Hello Siva, Can you please share with me what kind of errors it is returning to you? The rule is properly working for me, so I believe that maybe you've missed something when configuring the rule.

Hello, Check out THIS COMMENT on the Feature Request related to this functionality, describing how the Feature was implemented to allow more restriction to the available choices, but overall the intended functionality of the system is to be able to link to an epic in another project. Also, check out this other community…

You are welcome, Dana. Have a nice day.

You are welcome, Natalie. Have a nice day.

Hello Jennifer, First of all, welcome to the Atlassian Community! Answering your question: CSV import is intended to be a migration tool and not something that any user can use on a daily basis, so that's why the access is limited to the administrators. However, due to several customers requesting this feature, our…

Hello Natalie, Per your description, I believe you are facing the following bug: - Unable to delete request type associated with email requests This problem happens when your request type is associated with an E-mail request and the issue type is not associated with the project. Please, confirm if you are hitting this bug…

Hello Jens, I believe you are being impacted by the following bug: - SLA will not be triggered if custom events are used as the event to be fired upon issue creation Can you check if the workaround provided in the bug works for you: * Use the generic Issue Created event in the workflow transition for issue creation AND *…

Hello Maxime, Thank you for raising this question. I believe you are talking about the Quick filters available in the classic project's template. Is that correct? If that's what you meant, the new issue view available on the Next-Gen projects is still a lab feature on JIRA, so our developers are still working to implement…