Comments
-
@So Zoe - Can you answer please?
-
@Simon Gilmore - Please do not post on all posts that are already closed. Please open a new question so we can help you with your exact needs and scenario.
-
Hi Suporte - Yes, this is very doable. What messaging app are you using?
-
Glad you figured it out! And you are welcome!
-
Hi Tracie, If you are using different screens for those issue types, you will need to add the Story Points field to the screen(s).
-
Hi Lance - I am marking Tobi's answer as accepted. Let us know if you still have questions.
-
What do you mean by you can't add it? Is it not in the Field Configuration already? If you see that it is locked - then it is probably already there. Now, also add it to the screen used by the project. :-)
-
Hi Nikola, Not following what you are doing. If the Program Leader changes for the parent - how do you know what value to use for the Assignee? You are assigning the Program Leader from the sub-task to the Assignee field. Is that what you are trying to do? Is it because the Program Leader was blank in the parent and now…
-
Hi Quinn, Not sure of the ask here, but remove the fields from the screen used by the Epic work type. If multiple work types use the same screen, then copy the screen, rename it to Epic Screen add it to your Screen Scheme and then add it to your Work Type Screen Scheme and associate it with Epic. Then add the other fields.
-
As far as the setup - go to Settings > System > Audit log Then search on "group" or the group name. For where they are used, go to the Groups menu option on the User Management settings. Then click the information icon next to App. It will tell you which Atlassian product uses it but not much else. You should look under…
-
I am not familiar with team-managed JSM projects. That sounds painful to me. I don't know how advanced forms behave with that animal. Sorry
-
You need to discuss with leadership and get rid of 90% of those org admins. You only need a handful - probably no more than 3 for that number of users. You need at least 2 in case something happens to one of them. And you should handle permissions using Project Roles (Space Roles) and not groups if that's how they are…
-
Hi Nicolas - Welcome to the Atlassian Community! The type of field will determine what the syntax of the smart value looks like. For instance a dropdown is different text which is different from dates. What type of field are you working with? And I assume you have placed a value in the Field key for the field. What is that…
-
Once you add the rule/screen to the transition, it will not update the existing completed work items.
-
Hi @Julian Becher - Please post a new question so the specifics of your situation can be addressed. Be sure to include what type of project/space you are importing into - Jira Software, Jira Business, Company-managed, Team-managed, etc.
-
Hi Test Case, I am going to mark Tansu's answer as accepted. Please let us know if you still have questions.
-
De rien. Si cela a répondu à votre question, veuillez cliquer sur le bouton « Accepter la réponse » ci-dessus pour clore cette discussion. Merci !
-
Hi Audrey, Yes, this should be very possible. It really starts with your current workflow/process, and then you build that out in Jira. Use a Jira Software Company-managed project/space with Kanban template for the initial build. Then the workflow can be modified to do most anything you need.
-
Another user solved their problem by doing this: Go to fields configurations and find the system field Start Date [cf10015] and Due Date [duedate] and assign them to the screen of the project Not sure if that is the same thing affecting your or not.
-
Salut Jimmy ! Bienvenue dans la communauté Atlassian ! Vous devrez configurer la sécurité au niveau des tickets. https://confluence.atlassian.com/servicedeskcloud/configuring-issue-level-security-1097176572.html Cependant, cette fonctionnalité n'est pas disponible avec un abonnement gratuit (voir la note bleue dans la…
-
Thanks for sticking with that and posting the solution.
-
Hi Lisa, Take a look at this article and see if it sheds any light on it. You might want to book some time with Amy to discuss. https://community.atlassian.com/forums/Jira-articles/Notice-the-new-Jira-Business-timeline/ba-p/3165442
-
Hi Timothy, Trying going to Space Settings then People and see if you can add there.
-
Hi Michael - Welcome to the Atlassian Community! I am not aware of a way to grant permissions to edit the work items in the plan without giving them the ability to edit the plan itself. You might want to open a support ticket with Atlassian to get clarification. If you do, please post back here with the resolution for…
-
Hola Cinthya, ¡bienvenida a la Comunidad de Atlassian! Busca cualquier regla de automatización que pueda estar conectando las dos herramientas. Principalmente, verifica si se ha creado un webhook para la integración. Luego, deshabilita o elimina el webhook.
-
Hi Abilash, Tickets are not considered resolved unless the Resolution field is populated. This is most often done by the workflow used by the ticket to set the Resolution field using a Rule on the transition to the final status (Done, Completed, Canceled, etc.). Please update your workflow to add a rule on that transition…
-
Glad you got it working!
-
Hi Gerald, Take a look at this article and see if it helps any. You might even want to add a comment for Amy. https://community.atlassian.com/forums/Jira-articles/Notice-the-new-Jira-Business-timeline/ba-p/3165442
-
Thank you - and Merry Christmas to you!
-
And just to add to Bill's answer with some clarification - automation rules CAN do IF/ELSE. And Jira does recognize quarters as shown in Bill's answer. And you could create a variable with your formula and then use the variable identifier in the summary field get potentially get around the limit.