Looks like a good solution. The blurry part is sorting out all of the diff Jira products. We have “Jira” but I guess Jira Work Mgmt is a specific package.
Jira Work Management is now merging into Jira - they are now the same product. You now differentiate them by project type: software project (formerly Jira Software) and business project (formerly Jira Work Management),
I expect business team members can see the release info of JSW projects when those members don't have the JSW product access or licenses. They only have JWM product access.
Do you mean an automation rule that gets triggered whenever the form is submitted? I once did that by creating a new custom issue type for the form (aka whenever the form was submitted, it created the ticket in a custom issue type called formTask). Then I set my automation rule triggered whenever an issue was created with the type = formTask. Or do you mean building an automation rule within the form-creation screen??
@@ameliamelendez1574 You are correct, I need to trigger an automation on form submittion. I have done the workaround you described. But I need ~12+ forms and it isn't realistic to make new issues for every one. (even if I use the automation to change the issue type when done.)
This is AWESOME! This will definitely make our work easier to manage and see between our different teams.
Note that "Overviews" at the end of the video are no longer part of JWM. You now use Plans for E2E planning across projects.
Looks like a good solution. The blurry part is sorting out all of the diff Jira products. We have “Jira” but I guess Jira Work Mgmt is a specific package.
Jira Work Management is now merging into Jira - they are now the same product. You now differentiate them by project type: software project (formerly Jira Software) and business project (formerly Jira Work Management),
Nice demo, Abby! Thank you so much 🙏🏼
Well done Abby! 👍🏻
I expect business team members can see the release info of JSW projects when those members don't have the JSW product access or licenses. They only have JWM product access.
Please bring the "List"view to the JIRA Data Centre as well
Phoebe works for Atlassian!!
PERRRRRRFECT VIDEO
💙
Very good ❤❤❤❤❤❤❤thanks
Still don't understand why I can't build an automation to trigger of of a form.
Do you mean an automation rule that gets triggered whenever the form is submitted? I once did that by creating a new custom issue type for the form (aka whenever the form was submitted, it created the ticket in a custom issue type called formTask). Then I set my automation rule triggered whenever an issue was created with the type = formTask.
Or do you mean building an automation rule within the form-creation screen??
@@ameliamelendez1574 You are correct, I need to trigger an automation on form submittion. I have done the workaround you described. But I need ~12+ forms and it isn't realistic to make new issues for every one. (even if I use the automation to change the issue type when done.)
Walker Run
Cullen Club
COMPLETE TRASH - NEVER BUY From Atlassian EVER