Comments
-
Hi Sarah - Welcome to the Atlassian Community! I have not done an import since Jira switched over from using Issue to Work Item. You might try searching for Work Item Type.
-
No, there is only one layout. You can modify the layout, but not create a whole new layout from scratch.
-
You are welcome.
-
Okay, I am confused then. You just said that you had a field called "user" but did not mention what type of field it was. Then you said: This makes sense because the output "Person A, Person B" is indeed not a real user. So I assumed it was a text field. My apologies for that assumption. So if you are going from a…
-
100% on point with that first paragraph.
-
Hi @Donna Bahnfleth - Was James's answer able to help you?
-
Yes, but does the grumpy cat approve???
-
Hi @Amanda Warren - Did the above answer work for you?
-
Agreed - Atlassian appears to be spending significant effort trying to make Jira look like the cool kids in town instead of fixing bugs and adding long requested functionality. I won't call them features as they are normal functionality that should be there already but is missing. And within Atlassian all of this falls on…
-
Hi Emre - Welcome to the Atlassian Community! Since no one has responded to this, I suggest you open a support ticket with Atlassian. https://support.atlassian.com/contact/#/ Best of luck!
-
Hi @Sourav tulsyan - Welcome to the Atlassian Community! I am going to mark Vikram's answer as accepted. Let us know if you still have questions.
-
Add this to the beginning: {{issue.Reason}} Sujet: {{triggerIssue.key}} - {{triggerIssue.summary}} Date: {{triggerIssue.comments.last.created.asMediumDate}} {{triggerIssue.comments.last.body}}
-
Weird stuff! That being case, try adding a manual rule that instead of cloning the issue will create an issue and then you will need to list all of the fields you want "cloned" and copy in the trigger issue value. This would include the Assignee field. Hoping there are not a lot of fields on the screen that need to be…
-
Okay, that's different. Maybe try adding a branch with JQL for key = SCR=2330. Then under the branch an action to clone the issue. Then in the Clone action set the Parent field = trigger issue. Just doing this off the top of my head, so it might not work as intended.
-
Last desperate stab - who is the actor of the rule when if fires?
-
You will need a new rule for when the first sub-task transitions to Done to update all of the siblings.
-
Hi Gerald - Welcome to the Atlassian Community! Try setting up your Quarterly items as Epics and see if that solves it for you.
-
Hi Elango - Welcome to the Atlassian Community! I am not aware of a way for automation rules to create an Organization.
-
Team-managed projects are very limited in what they can do. And yes, you would need to be a Jira Admin to be able to properly manage Company-managed projects. Does the Epic in your project have a different workflow than the other work item types? Can you share some screen shots?
-
Hi Seda - Welcome to the Atlassian Community! Approvals can be done in both JSM Standard and JSM Premium. You do not need to get Premium just to do approvals. Approvals can be granted by JSM Customers, who do not need to have a license. But members of your team who are doing the actual work of updating and transitioning…
-
Hi Leonid - Welcome to the Atlassian Community! Be aware that if you change the Work Item Hierarchy, it will be changed for the entire organization and there is only one Hierarchy. That being said you can do the following: To Create Epic work item type as Level 2 * Rename current Level 1 name from Epic to Feature * Click…
-
Hi Antonia, If the two work items share the same workflow, then you can just update the work item type with the automation.
-
Hi Brent, You won't be able to update the Assignee field if the value is not a real user. I would suggest you use the user's email address for the value Users field, then it would work. Or update the Component to have the default assign it to a particular user for that component when a new work item is created. Be sure to…
-
Hi Sheila - Welcome to the Atlassian Community! Not it's not possible with any subscription right now. Calendars are by project. You could probably create a Calendar in Confluence that uses work items from multiple projects. https://support.atlassian.com/confluence-cloud/docs/create-add-and-edit-calendars/
-
Hola Alan, ¡Bienvenido a la Comunidad Atlassian! Hay una notificación integrada que envía estos correos electrónicos y que debes desactivar. Esta notificación envía un correo electrónico a todos los miembros de la misma organización que el reportador del ticket. Ve a Configuración del Proyecto > Notificaciones >…
-
Hi Soubhagya - Welcome to the Atlassian Community! Issue layouts are based on a combination of Screen and Issue Type. You can modify using the Configure button at the bottom right of an issue screen. Then you can copy the layout to other projects for that same screen and issue type.
-
Hi Beth - Welcome to the Atlassian Community! I am not aware of a way to do that. There is an open feature request ticket that might apply that you can vote for and follow. https://jira.atlassian.com/browse/JSDCLOUD-16287
-
I like most traditional card games - Hearts, Spades, Rummy, etc. Also, Settlers of Catan, Pictionary, Balderdash, Telestrations and several of the others already mentioned.
-
Hi @Cyril - Did Vikram's answer help you?
-
Hi Max - Welcome to the Atlassian Community! If you create an issue type for Epic it should show on the board for a Team-managed project. The real answer is to quit using Team-managed projects and switch to Company-managed projects.