Trudy P Claspill Community Champion

@Sravan Indukur Refer to this article for more information about what is tracked in the audit log. https://support.atlassian.com/jira-cloud-administration/docs/audit-activities-in-jira-applications/ It does not include every activity related to individual issues.

Hola @Wilber Ballestero , La fecha y hora de creación del problema ya están documentadas en el campo Fecha/hora de creación. ¿Qué problema intentas resolver agregando esta información a un comentario? --- Hello, The date and time of issue creation are already documented in the Created date/time field. What problem are you…

Hola @Wilber Ballestero , El problema existe en Proyectos. Los tableros son solo una forma de ver y manipular los problemas. Los tableros muestran problemas según un filtro asociado. El problema no está "en" el tablero, simplemente coincide con los criterios de filtro del tablero. ¿Exactamente cómo trasladas el problema a…

Hello @Gonzalo V In order for a user to be able to access the product they must be a member of a user group that has been granted access to the product. As a Site Administrator you should be able to access this information by going to admin.atlassian.com and looking at your site. You should be able to see something similar…

How have you confirmed that you are looking at the correct field configurations and screens to ensure the field should not be present?

Hello @Manjunath MP Welcome to the Atlassian community. A Jira Server license is perpetual. The system will continue to operate in its current manner after the license expires, but you will no longer be able to get support from Atlassian for it. If your plugins are not providing integration to external products, they also…

Okay, maybe that's the explanation, rather than parallelism. ;-)

Hello @Lauren Briskin I suspect that somebody has change the Inward and Outward Descriptions associated with the Clones link type. Below are the default descriptions for the Clones link type. The value in the Inward Description will show in the issue you started the Clone operation from. The Outward Description will show…

Hello @Neil Williamson Welcome to the Atlassian community. I don't fully understand it, but branches can be executed in parallel and this appears to apply to Conditions also. See this issue report and the one which to which it is linked. https://jira.atlassian.com/browse/JSWCLOUD-22680 If you want to ensure that the two…

I did a quick test and it doesn't appear that the field can be referenced using "Story Points[Number]" as the field name in an Automation Rule. So you will have to find the custom field identifier for it. Refer to this document: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Search…

No hay opciones para horas hábiles, minutos o segundos. Puede tomar los resultados del uso de la opción de días hábiles y multiplicarlos por la cantidad de segundos en su horario laboral para un día hábil. Ese no sería un cálculo perfecto, ya que los tiempos especificados en los campos podrían ser parte de un día hábil. Si…

Both very odd circumstances. I recommend that you have your Jira Administrators open support cases directly with Atlassian on each of these. And it would be great if you can report back here what you learn.

Hello @Joe Yee Fung So far I have not found any way to do this, nor have I yet found a change request in Atlassian's public backlog for this feature. Can the other user see the board? Have you shared it with them (shared the filter, made them an administrator of the board)? I wonder if you do that, if the other user would…

Hello @ROD_GILBERT Welcome to the Atlassian community. I am not able to recreate your issue. I am able to select the 9/4 date when the month of August is shown. Have you tried advancing the calendar to show the month of September? There is no native global non-working days entry that could cause this, per…

Hola @Wilber Ballestero , ¿Qué unidad de tiempo desea utilizar para los resultados? ¿Está utilizando campos de solo fecha o campos de fecha/hora? Existe una unidad de tiempo "businessDays" que considerará únicamente los días hábiles al calcular la diferencia. Esa opción aparece en la documentación de la función diff.…

Olá @Vinicius Souza de Oliveira , Bem-vindo à comunidade Atlassian. Se você está falando sobre remover o valor de uma única subtarefa, você pode tentar editar manualmente essa subtarefa e limpar esse campo. Se você quiser que a automação pare completamente de funcionar para que as informações não sejam mais copiadas para…

Hello @cmartin_wilson Welcome to the Atlassian community. You simply cannot create a board until you have something to reference - either a project or a saved filter. When the UI tries to display a board it is going to automatically try to load the issues that the board should display based on the underlying filter of the…

Thank you for that image. That is not a marketing email. That is an invitation to you to access a specific Jira instance owned by somebody. If you feel that you are being sent these emails erroneously you can forward them to https://www.atlassian.com/trust/report-abuse and Atlassian will investigate the source.

To clear the Flagged field in Automation, use the Edit issue action, select the Flagged field, and simply leave the value field blank.

I believe (but have not fully tested) that the Security Schemes apply only to licensed Jira users and Jira Service Management agents/team members who are viewing the issues through the Jira UI. I don't believe that the Security Schemes apply when issues are viewed through the Service Management portal. For people who are…

Hello @Alex Saunders Using the Mark As Done option will hide the Epic from the Epics Panel while still keeping it editable and searchable. "Mark as Done" sets a secondary status field that is only in Epics called "Epic Status". Unfortunately this field doesn't show in the issue details, and there is no "Mark as Not Done"…

Hello @Patricia Nora Thank you for that explanation. That was very helpful. I can think of at least one way to handle this with automation that might work. There is a Create Lookup Table action. This is a table of key/value pairs. You would create an entry for each product. Each month you would manually update this table…

What do you mean you "can't choose"? Do you not see them among the listed templates? Is there a link below the listed templates to "Show more"?

I am not able to recreate your scenario. I created a new standard issue type - New Feature at hierarchy level 0. I did not explicitly add it to the issue hierarchy. I added it to the Issue Types scheme that is used by the project. I created a new Epic issue in the project, and I do see the new issue type as an option for…

The log file documents that issues are being found by the Lookup, per the notes on the right side. But, just to confirm can you add another Log action after the Lookup to print out Results count: {{lookupIssues.size}} Given that the print out of {{lookupIssues.Story Points.sum}} is zero, that is an indication that there is…

Automation for Jira includes a Delete Issue action. Use that.

That will have a value only after you have executed a Lookup Issues action. You need to insert into your rule after that action.

Hola @Wilber Ballestero , Jira no admite la configuración de permisos de edición por campo. ¿Está trabajando con problemas en un proyecto administrado por equipo o un proyecto administrado por la empresa? Si está trabajando con un proyecto administrado por la empresa, existe una solución alternativa para eliminar los…

Do you expect the issue to remain visible to the customer through the portal after you convert it to a subtask? Are you considering the second option to clone it into a subtask and then delete the original issue? Automation does not support the Convert option nor the Move option. In some cases you can work around that by…

Hello @Sujitha.Krishnan Can you show us a screen image of one of the linked issues showing the Story Points field with its value? Can you try using the Log action to print into the Audit Log the value of {{lookupIssues.Story Points.sum}}