Petter Gonçalves Atlassian Team

Hello Eitan, You can use the Previous State Validator to achieve your need, selecting which should be the previous status of the issue to allow the transition.

Hello Tina, You are correct to say that you must add the e-mail address as a licensed user in the system to receive notifications. Additionally, the mentioned user must have a valid JIRA license and be added in the browse project permission and in the issue security level (If there's any), since the notifications can…

Hello Maher, Welcome to Atlassian community. All the restrictions that you can add/remove from groups of users are displayed in the permission scheme of the project (Project Settings > Permissions). You can absolutely restrict some users to only comment or modify the status of the issue by restricting them to the Add…

Hello Natasja, Actually, the expected behavior is that the default issue type should be always the first option when creating a new issue, however, there's a bug in the application which is causing the last used issue type to be selected instead of the default. Although we don't have any workaround for the bug at this…

Hello Esther, I took some time searching about the Rally application format options and I found out that it uses Markdown formatting, which is the same format that JIRA uses in the new issue view (The old issue view uses Markup format). That been said, have you tried to copy your Rally text and paste directly in the JIRA…

Hello Faisal, Welcome to Atlassian Community! Can you confirm if you are using the new issue view? Since the new issue view is still a beta feature on JIRA, we are still working to implement some features, including the ability to copy/paste attachments directly from the issue view. For this specific matter, we have a…

Hello John, Welcome to Atlassian Comunity! Can you let us know if you are using JIRA Cloud or Server? If it's JIRA Cloud, are you using next-gen projects or Classic projects? In the old issue view, the sort of comments can be changed by clicking in the arrow as displayed in the screenshot below: In the new issue view, as…

Hello Yohan, Welcome to Atlassian community! You know, for some questions in your description we don't have a single and definitive answer, however, I think the information below will definitely help you: 1 - The most important thing to keep in mind before you migrate from JIRA Cloud to Server is: - Make sure you have…

Hello Rob, Thank you for confirming. Although you can set the SLA value of a project you can't see in the JQL, the JQL query should return only the issues from the projects which you can see. That been said, the expected behavior is to return nothing in the query if you set an SLA of a project that you cannot access. Let…

You are welcome, Tina. Indeed, the new issue view and next-gen features are on the top list of our development team prioritization, so I believe it will not take too long to be implemented. Have a nice weekend!

I'm glad to know you were able to find a better solution, Dan! Have a nice weekend and please don't hesitate to contact us again every time you need. :)

Hello Rajesh, Unfortunately, it's not possible to calculate the days between two date fields in JIRA, however, there are some plugins which provide you with this functionality. Can you please let us know if you are using JIRA Cloud or Server so we can search for some options that you can use? For now, check if the Scripted…

Hello Michael, Actually, Stories can be moved in a board by simply dragging and dropping them in your board columns. The only requirement to accomplish that is the board columns must be mapped with the respective statuses of the Story. In order to better understand your request, could you please provide us a screenshot…

Hello Koteswararao, When you say "Average", you are meaning the average time between the creation and resolution of multiple stories, is that correct? You can use the Average Age Chart Gadget to return this information. Here are the steps: - Create a filter to return the issue(s) you want - Navigate to your dashboard > Add…

Hello Robert, Unfortunately, the current Official Mobile App for JIRA Service Desk only allows Agents to perform some internal actions, not displaying any functionalities to customers. We have a feature request created to implement an App which includes the customer portal and other functionalities to customers: - Use JIRA…

Hello Dan, The query you mentioned is returning, in fact, all the tickers resolved between the start of the current day and the start of the next day, but not yesterday. I'm not sure if you are resolving your tickets in the next business day and that's why you are using that query, but I think the best option to return the…

Hello Brenda, Thank you for raising this question. The hours between Original Estimate that are not matching is not a bug, but a behavior that you can achieve if you perform some steps. By default, the remaining time will have the same value as the time estimate when you configure it unless you manually set a different…

Hello Melissa, I understand that you would like to allow external users that do not have a license to create tickets in JIRA and get notified about its updates. Is that correct? The application which would fit for your need is JIRA Service Desk. With JIRA Service desk, you would be able to create a customer portal where…

You are welcome, Meredith. Have a nice day!

You are welcome, Franklin! Have a nice day. :)

You are welcome, Davina! Have a nice day. :)

Hello Franklin, Thank you for your detailed description. I think the Issue Statistics Gadget can help you achieve your need, however, you will need to take some time to work through the steps. Here they are: 1 - Create a single filter for each group of users, specifying each user from the group in the JQL query as the…

You are welcome, Mattias! Have a nice day. :)

Hello Andrew, Welcome to Atlassian Community! Indeed, there are some features which are quite different between Classic and Next-gen projects and can cause some incoherency and data loss when switching the key from one type to another. These particular features are properly listed in this documentation, together with clear…

Hello Jimmy, The error message informing you that you must have a valid JIRA license to create JIRA tickets usually appears when you have not configured a default reporter in your e-mail handler, however, you are trying to creating an issue from an external e-mail which is not added as a licensed user. Can you confirm if…

Hello Tina, Unfortunately, the display you are needing can only be achieved in the old view of JIRA. The new issue view is still a beta feature so it does not have all the features available in the old view, like the displaying applicable by the jira.table.cols.subtasks parameter. If you would like to get it working in the…

Hello Eitan, Could you please let us know the Priority field you mentioned is the priority system field added to JIRA by default or is it a custom field created? I ask this question because this field does not have the "None" option you mentioned, at least not by default. Assuming we are talking about the system field, the…

Hello Claudio, Thank you for reporting this issue. Per your issue description, there are several possible reasons for the mentioned problem, so I kindly recommend you to perform the following steps for now: 1 - Reproduce the problem and check in the Javascript console of your Browser if the error returned is not the same…

Hello Mattias, You are correct to say that It is not possible to migrate issues together with its comment restrictions, unfortunately. In fact, we have a feature request opened to implement such functionality: - Visibility of comments from CSV import Feel free to vote and watch the suggestion to increase its priority and…

Hello Caroline, Welcome to Atlassian community! Indeed, the Audit logs of JIRA does not register creation, changes or deletions of issue types. We understand that this is a piece of important information when investigating anything in the background of the application, so we created the following feature request with our…