Petter Gonçalves Atlassian Team

Hello Tony, Thank you for reaching out. The quick answer to your question is: Yes, you can have both your internal team logged with SAML and the third-party users logged with their respective Atlassian Accounts, you just need to have properly invited them to your site or configured your instance in a way they can self…

Hello Sergey, Welcome to Atlassian Community! Just to make sure we are on the same page: When you say the option to create sub-task using the "inline" field, you are talking about the inline option of any Story (As displayed in the first screenshot) or in the inline option of the board (The one that is mentioned in the…

Hello Fernando, Welcome to Atlassian Community. There's a couple of possible reasons that could be causing your activity Steam to stop loading. Please, check the following details to properly troubleshoot the problem: 1 - If you have enabled HSTS, the activity stream might not load as mentioned in the bug below: - Activity…

Hello Veronika. Thank you or your answer. Could you please provide us more details about why your customer does not want to use sub-tasks? Is it only because of the name "Sub-task" or is it because of any functionality? Just to give you more context about my question, you can create custom sub-tasks in JIRA, that you can…

Hello @rhayje Thank you for reaching out. Per your description, I believe the ideal solution would be to ask someone with access to the workflow to properly create a new status and add it to the backlog, properly separating the "backlog" and "open" issues. apart from that, the only thing you could do to organize and make…

Hello Ismael, Welcome to Atlassian Community! Please, check the steps below to properly troubleshoot the problem: - Navigate to your Next-gen project > Project settings > Features > Check if the estimation feature is turned on - Double-check if you are using the correct Story Point estimate (Created by JIRA) to estimate…

Hello Peter, Thank you for reaching out. I believe you are talking about the triggers available for JIRA that will fire an issue transition, configured under Project Settings > Workflows. Is it correct? If I understood it properly, I'm afraid we don't have this kind of trigger for JIRA workflows at this moment, although we…

Hello Chris, Sorry to hear you are facing this problem. In fact, I was able to reproduce the same problem when configuring the post function in the Create transition of the workflow, while in the other transitions it works just fine. In order to get it fixed, I reported this behavior as a bug with our development team:…

Hello @Balamurugan Thank you for reaching out. Could you please let us know what is the gadget you are facing this problem and provide us with a screenshot of the view so we can better understand what is the problem you are facing exactly? More specifically, provide us with the steps you are taking to reproduce the…

Hello Jan, Thank you for reaching out. Actually, you can change the options added to your Select list custom field by following the steps below: 1 - Navigate to JIRA Settings > Issues > Custom Fields > Find the select list and click on Configure: 2 - Click on Edit options: Let me know if this information helps.

Hello Veronika, Welcome to the Atlassian community! Per your description, I understand that you are using three hierarchies here: Epics > Features > Tasks. By default, JIRA works with three hierarchies as you are configuring, however, it would be: Epics > Standard issues (Task, Bugs, etc) > Sub-tasks. That being said, I…

Hello @s-sainik Welcome to Atlassian Community! The error you are facing seems to be related to JIRA permissions, which is a different problem from the one mentioned above. I recommend you to contact your site-administrator and ask him to check the following: 1 - Check if your user is configured with the correct product…

Thank you for your feedback, Elizabeth. Indeed, I must say that the development team responsible for the Next-gen template is currently collecting feedback and working to get the application with the best functionality possible. If you are interested to see what they are planning to implement next, you can check our…

Hello Mike, Thank you for reaching out. Per your description, I believe you are using a next-gen project and you would like to consider the issues in the second-most right column as done in your project, so it can reflect in your Epic roadmap progress bar. Is it correct? Although you can not select multiple columns to be…

Hello Patryk, Welcome to Atlassian Community! I understand that you would like to configure the Roadmap feature of Next-gen projects (See picture below) with issues of multiple projects at the same time. Is it correct? The roadmap feature of JIRA next-gen is based on the board filter, which can not be changed at this time,…

Hello @Keanu Concepcion Welcome to Atlassian Community! I believe the best option to get all your teams working together in the same project allowing them to see each other work but have an organized way to identify/filter which issues belong to what product would be to use the components to define your products, all in…

Hello Matt, To add existing issues as a child of another, the issue must be a sub-task since it have some particularities not present in other issues. A Standard issue can not be added as a child of another standard issue. Now, if you want to convert a standard issue as a sub-task of another standard issue, you can follow…

Hello @Luis Gonzalez Thank you for reaching out. I understand that every time you transition an issue that is not assigned to you, you become the assignee of that issue and the correct assignee is removed. Is it correct? This is definitely not a default behavior of JIRA, so I believe some automation apps or a post function…

Hello Michael, Thank you for reaching out. Unfortunately the wildcards functionality was not implemented for JIRA Cloud yet, however, we understand that this is a useful feature and create the following feature request: - JQL - Add wildcard functionality to versions Feel free to vote and watch the suggestion to increase…

Hello Elizabeth, Thank you for reaching out. As you can see in the documentation, the Next-gen template was designed for those users who felt overwhelmed by the complexity of JIRA Classic template and requested a simpler option, straight to the point with fewer options of customization. That being said, it is not possible…

You are welcome, David. Have a nice day!

Hello Ricardo, Welcome to Atlassian Community! I think I have not completely understood your requirements. Could you please clarify if you would like to send notifications when something changes in the tasks of a specific Sprint (Assignee, description, etc) or when something changes in the Sprint itself (Start date, end…

Hello Andrew, Thank you for reaching out. I believe the best way to identify if an issue is being moved from Sprint to sprint would be by using the Sprint report and check the section "Issues Removed From Sprint" in the bottom of the report: Changing the Sprint number at the top, you will be able to have a clear view of…

Hello Darya, Thank you for reaching out. I understand that you would like to export your issues in a template format, where you can configure a determined format with customized details in the header, is it correct? Although this procedure is not officially supported by Atlassian, the word export functionality can be…

Hello Chris, Doing some search in Atlassian documentation, there are no issues documented with the Bitbucket links (Branches) when migrating issues from classic project to Next-gen. In fact, the link works in the same way in both templates, so that should not give you any errors with the Classic to next-gen migration.…

Hello Jeremiah, Sorry to hear you are facing this problem. Indeed, we have identified this behavior in Jira cloud and reported a bug with our development team in order to get it fixed: - Certain field descriptions are rendered between HTML paragraph tags Feel free to vote and watch the bug to receive notifications about…

Hello David, Thank you for reaching out. Per your description, I understand that you would like to know how you can add or remove the project roles and groups that you can restrict your comments on the log work description, as displayed in the screenshot below. Is it correct? If that's what you are talking about, this…

Hello Nodar, Thank you for reaching out. I understand that when a Service Desk ticket in your software board when you are the approver of the mentioned request, you are not being able to transition it to "approved" status. Is it correct? We will need some more details to better troubleshoot your issue, so please try the…

Hello, Although this is a little bit late, this issue usually happens when the user can not create the sub-task because of the following reason: 1 - The Sub-task is configured with a required field, that can not be set using the inline option (See JRACLOUD-69222) - This might not be your case if other users are able to…

Hello Deanne, Welcome to the Atlassian community! The error you are describing usually happens when the issue-type you are trying to create is not configured with the Epic Link field on its screens, as mentioned in this feature request: - Misleading error message when the user cannot create inline child issue for an Epic…