Fernando Eugênio da Silva Community Champion

Hey! This could be because the filter configured for the board is not configured to handle this issue status or this status is not mapped to any column on your board. Can you check these two details and return? If it still doesn't work, please come back with screenshots of the board settings for us to evaluate.

@Shaveta Shukla Sometimes some mailing lists fall into a kind of limbo on Atlassian's servers and need the team to clean up these emails in order for them to receive notifications. The best scenario for this case, as they are new guest users, is for you to open a support ticket for Atlassian and provide the emails of those…

@Guillaume Gaudonville Have you already checked the permissions schemes for your project? Do the following: Access the project settings and click on "People", add your user in the project role "administrators". Then go back in the project settings and see "Permissions", ensure that the project role "administrators" and…

@kevin Muñoz Puede crear una automatización y usar el disparador SCHEDULE. En él incluye el JQL en este formato: project = XXXX AND issuetype = Story AND updated <= -2d AND Sprint is not EMPTY AND statusCategory != Done Esto solo afectará a los problemas que se hayan movido en los últimos dos días o más y que aún no se…

@Alejandra González Were these tickets resolved after this flow configuration was applied? If they were resolved prior to this setting, you may need to consider upgrading their resolution or making a bullk change. Also check if there is no automation clearing the value of the "Resolution" field or if there are not two post…

Hey, Jack! I believe that Vicenzo's idea here is to put only one "Team Leader" to license internally in Jira and this change the "Reporter" of the issues. Aiming at this concern with a licensed user and other accesses that this can compromise, I suggested the use of automation to change the value of the reporter through a…

@Vincenzo man In order for you to enable a client user to edit you need to give this client internal permission in your environment as a "jira-servicemanagement-user". After that, you need to go to "Project Settings" > Screens > Select the "Screens" set of the issuetype and add the "Reporter" field in the "Edit" and "View"…

@Anna Herbener Welcome! I believe that in this case the problem is in the type of branch used. In an easier way, I got the result. I made it work using JQL. I created an Epic named Linux and made it work like this: You need to put Epic's summary condition in the JQL so that it reads that as the validator for the linked…

@Sari If you plan to follow the concept of hierarchies, you need to change the use of tasks to sub-tasks, so the hierarchy in Jira would look like this; epic story sub-task If you only plan to have tasks associated with your Story, you can do the following: When creating the task, locate the "Linked issue" field, insert…

@Vincenzo Users who have permissions to be only "Customer portal", cannot indicate another person to be "Reporter" of the issue. This permission is only available to users who have a "jira-service-management" license within the environment, which allows them to access Jira internally and manage the portal's clients when…

@Alfred Lombardi For the list or timeline concept this is not possible yet. A similar view to this would be roadmaps, available for Scrum projects in Jira Software. But I'm glad the plate concept helped you. Please click "Accepted Answer" to ensure that other users can locate these tips if they have questions similar to…

@Albert Nkansah Glad this helped. If you can click "Accepted Answer" in my answer, it will help other users with the same problem/question as you to find this solution faster. Take care of yourself. best

@Albert Nkansah For this process, you will initially need to ensure that the "Epic link" field is set as an "Editable" field in Jira. To do this, do the following: Open the project; Click on "Project Settings"; Click on "Screens"; Select the "Story" issuetype and click on the "Edit Screen" screen; At the bottom of the…

@E-Sign This must be project permissions. You can solve it in a more practical way as follows: Access the project: Click on "Project Settings"; Click on "People"; Click on "Add people" Put your user as administrators. Or you can go to project settings and "Permissions" and configure your user for project permissions.

@E-Sign I understood! On this screen you won't be able to list the issues by hierarchy from "Story > Sub-task" because this is a Jira issue queue screen, so you can only enter display data in it in order of status, creation, reporter, etc, but not list according to hierarchies. The most you can do is sort by issuetype from…

@E-Sign Welcome! Where exactly do you want to apply these visibility settings? On a kanban board, in Advanced Roadmaps?. Can you share this information and other screen details? So we can help you in the best way.

@Alfred Lombardi Welcome! For you to view by epico click on the board settings, access and perform the settings below: When accessing the board, this will be the view with the issues below in their respective columns If you still need to organize your query by JQL, just apply one of the following expressions to the end of…

@Natalya Karabelska Welcome! You need to review the filter that is applied on this KANBAN board. Do the following: - Access the board settings by clicking on the "Board" option and "Configure board" in the upper right corner. - Then in general, see the filter being used for this board. If the filter includes Epics, then…

@Siva , Please click on "Accepted answer" o ensure that others will find this help easier

@Siva Thanks for the prints. I have news! I noticed that you are working on a Team Managed template project, this is a simpler settings project template, so for you to insert the sub-task you need to create it by clicking on "Add a child issue". The native "Create Sub-task" option is only available for "Company Managed"…

@Siva Welcome! Please check the following: Access the project settings; Click on "Issue Types"; Be sure to add the issue type "Sub-task" in the project's issuetype schema. After that, try to create a Story and validate if the option to create a sub-task is already available. If it doesn't work, come back with a screenshot…

@Markus Oberndörfer This may be possible if you use a plugin like Jira Misc Workflow Extensions. You would need to go into your workflow and the 'create' transition, click on 'Validator' and configure with the JMWE app these issue creations validations. Natively I don't know if it's possible to perform all this specific…

@Francis Castro There are two ways this problem is occurring, but from your description, I believe it is because the users who are accessing the link do not have an active Jira Service Desk or Jira Software license. If the link you send is taking them directly to the customer portal, these users have probably lost their…

@Martina Moring Burndown is affected when the issue meets the value "Resolution", this is the data factor for burndown. We usually have more access with burndown and this data view when we've completed a sprint. So I would recommend that if you can create a sprint ghost just to indicate some test issues and fill in the…

Hey, @Edd drew . There are some help pages and suggestions for using smart values here: https://support.atlassian.com/cloud-automation/docs/what-are-smart-values/ https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/…

@Martina Moring Burndown visualizes when the issue arrived in her "Resolution". For this to work as you expect, you need to do the following: In the flow, check if only for the status "ready to deploy (beta)" there is a post function indicating the resolution of the item. And for the other statuses of "ready for review"…

As they are customers of different companies, you can start to work with "Organizations" and register each customer in their appropriate organization. Every organization would be a "Company". Example: Organization: All Star Customers: Jhon, Lisa, Mary Whenever one of them creates a ticket and selects the organization, all…

.

@Amministratore Jira You can also try the following: If issues are always cloned into a specific status, you can put an "All" transition on it, and direct the clone to do so. The problem with clones using automation is that in flows, it only follows the transition lines step by step, they cannot read other transitions…

@Foroud Saraji You really can't identify any error lines downloading the ZIP in the Troubleshooting and Support tools tab? This would help you understand if the problem is in the environment or in the database. Try this or when the error you indicate appears, click on "see details" to see the error logs. Usually the Server…