Petter Gonçalves Atlassian Team

Hello, The Atlassian Account page (id.atlassian.com) is intended to don't display the dashboards and sidebars referent to any sites the user might be added to. This behavior is not a problem, but an expected configuration since a user can be added to multiple sites and it would not make sense to display the site data on…

Hello Hamza, Welcome to Atlassian Community! Per your description, I think you are using JIRA Application with Slack, is that correct? Could you please confirm if you are using JIRA Cloud or Server? There are some add-ons that you can use to manage JIRA tasks directly from Slack. The one I was able to test and is available…

Hello Justin, As an Admin, you can manually invite any users even if they are not added in the same domain configured to your organization, although you will not be able to manage their accounts if they are not part of your domain. You should be able to perform it right away by manually inviting them on User Management >…

Hello Manu, Welcome to Atlassian community! Can you please let us know if you are using JIRA Server or Cloud? I understand that you would like to have a countdown timer just like the SLAs of JIRA Service Desk, so you could see how many minutes you still have until the expected resolution time of the issue. Is it correct?…

Hello Bryan, You are correct. The priority of issues keeps displaying as the default in the view screen even if you remove it. We have created two feature requests to change this behavior, however, it was not implemented because of the low number of requirements on it: - Remove "Priority" field completely from JIRA Issue…

I'm glad to know you were able to identify the problem's cause, Gianfranco. Have a nice week and please don't hesitate to contact us again everytime you need. :)

Hello Ofer, Actually, both queries provided have come up with the same results for me, as you can see in the screenshots below. I only changed the project to TS to be an existing one in my instance: In fact, both queries are correct and it's expected that both return the same results for you. That been said, could you…

Hey @Thomas Deiler Your answer is perfectly complete. :) I'm sorry that I didn't see it before posting my answer. Good job man!

You are welcome, Elle! Have a nice week.

Hello Giancarlo, Welcome to Atlassian Community! Since you mentioned request types, I believe you are using JIRA Service Desk, is it correct? You should be able to achieve this functionality by creating the following Automation rule for each Request type: For more information about automation rules on JIRA Service Desk,…

You are welcome, Riley. I must confess you that I may have not properly understood what feature you are looking for that is available only for Classic projects and not on Next-gen. If you could give us more insight about that (Maybe screenshots would be helpful), I would really recommend you to create a suggestion on our…

Hello Sonia, Welcome to Atlassian community! Yes, it is possible to use JIRA to trade messages about a specific subject by using comments on issues. You can even integrate your e-mail channel to JIRA so when you send an e-mail copying your JIRA e-mail address, an issue should be automatically created on JIRA and all the…

Hello Antônio, Can you please provide us the JIRA version that you are currently using? For all versions developed after 2012, JIRA already has the functionality to create a transition that goes to the same status it came from (Loop Transitions), just like explained in the suggestion you mentioned. The steps to perform it…

Hello Heath, Welcome to Atlassian community! It's expected that an issue keeps appearing in the done column of the board once it is completed for 14 days and then removed from the board view. This is how the board is rendered for Next-Gen projects, however, we have created a feature request to allow users to choose if they…

Hello Riley, Welcome to Atlassian Community! There are some ways/fields you can use to filter by issues from older sprints and by issue type in your Next-gen projects using JQL filters. Here are some of them: 1 - You can use the parameter closedSprints() and order the issues by Sprints: Project = xyz and sprint in…

Hello Murat, Welcome to Atlassian Community! To properly link stories with a specific Story in your CSV file, you must place the issue id of the "sub-Stories" in the column "Relates to" of the "Main-Story", however, you must use different Issue IDs for each "Sub-Stories". That been said, you can not add the same value "1"…

Hello Anjali, Welcome to Atlassian community. Could you please provide us more details about the problem you are facing? What application you are using to reproduce this problem - JIRA Cloud or Server? The Epic Link field works to properly link an issue to an Epic. Can you please provide us the steps you performed to…

Hello Ofer, Welcome to Atlassian Community. The query you are using should return all Stories of project XT that are currently added to your Active Sprint. In other words, it will only return issues that are added to an "In progress" Sprint that was already started, but not completed. That been said, can you please give us…

Hello Stefan, Could you please provide us more information about the approach you mentioned below? There is a project independent board what filters these issues and makes them available to the Jira projects of both parties. This approach enables us to create an issue only in one of the projects and to make it visible to…

Hello, Unfortunately, our developers have not provided any updates about this bug yet, however, you can directly comment on the reported bug to verify if they already have anything about it: - Wiki Style Renderer does not work for custom fields Cheers.

Hello Matt, Please, allow me to clarify the difference between both fields: The parent ID is a general issue identifier field which is immutable, while the Parent key can be changed by the user (Moving issues to a different project, importing a different value, etc). About the error you are facing, please check if you are…

Hello Elle, To include the Epic to your filter, you just need to add the parameter OR followed by issuekey = POLYDECK-17. The query would be configured like this: project = POLYDECK and "Epic Link" = POLYDECK-17 or issuekey = POLYDECK-17 Let me know if it works for you.

Hello Anders, Welcome to Atlassian Community! In JIRA, when an issue is created it can only be directed to the first status in your workflow, however, you can easily configure an automation rule to move the issue to the next status if it was created by e-mail by using some plugins. That been said, my personal…

Hello Andre, Welcome to Atlassian Community! Thanks a lot for letting us know about this problem with the Roadmap feature of next-gen projects. We have properly reported this behavior as a bug to our development team here: - Next-gen projects: The date indicator line on the roadmap displays an incorrect date when using a…

You are welcome, Ketil! Have a nice day.

Hello Ketil, Welcome to Atlassian Community. Unfortunately, you can not add multiple statuses to the done category in next-gen projects as you need, however, we have opened a feature request to implement it: - Ability to customize status category in Next-gen projects Please, add yourself as a watcher and vote on this…

Hello Jeff, Indeed, the new issue view of JIRA does not have the convert sub-task to issue feature, so we created a bug to fix it: - New Full View Issue Experience eliminates convert subtask to issue feature Please, watch and vote the feature request to receive any updates about it and also increase its priority. Let us…

Hello Josh, In fact, we have identified this exact behavior with the next-gen projects and reported it as a bug here: - Flags are disappearing in new next-gen projects Please, add yourself as a watcher on the reported bug to be notified about any updates from the developers working on its fix implementation. Also, feel…

Hello Emer, The scenario you are needing cannot be achieved using only JIRA, however, there are some plugins that give you this functionality. I recommend the plugin Automation for JIRA Cloud where you can configure simple rules to: 1 - Automatically create tickets in a different project 2 - Clone fields when a new issue…

Hello Karim, It seems that you are talking about the obsolete User Permission Validator, is that correct? Actually, this validator it's a leftover from older versions of JIRA. It is mainly here for the users who were using it in older versions and still need it. This validator used to give you the option to validate that a…