-
Bug
-
Resolution: Timed out
-
Medium
-
15
-
Severity 3 - Minor
-
0
-
Summary
- User tries to add a Global template to a create from template macro inside a global template, the user has to specify the SPACE key to populate the Template List.
Steps To Reproduce * Create a Global Template
- Insert a Create from Template macro
- Specify the template you want to create from the drop-down list.
Expected Result
- Template list will load with all the global templates.
Actual Result
- Inside the macro, the user first needs to specify the SPACE KEY, and then the template list will be populated with all the global templates as well as the Custom Space Template.
- The user selects the required Template(Global/Space template) and deletes the space key and save the macro.
- When he tries to edit the macro, the template list will be EMPTY with no list populating the drop-down. Video Attached
When we try to create a page using this saved macro(with empty template list), the page will be created with the specified template we have given before deleting the space key.
- is related to
-
-
- Closed
-
-
CONFCLOUD-66313 User should be able to use Create from Template Macro in global template
- Closed
- relates to
-
-
- Closed
-
-
-
- Gathering Impact
-
[CONFCLOUD-59698] Template list won't populate unless Space Key is defined in Create from Template Macro, inside a Global Template
We are currently migration to Cloud and are facing this issue. I was recreating our global templates when I noticed, that filling in a space key is mandatory...
Therefore "by default, the current space" is not achievable.
Again, to clarify: i am editing a global template that uses the "create from template" macro. This is a main feature that our whole company is using regularly.
Any updates on this?
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
We do have the same issue except we can't creaty new pages with the button in any space. So this seems not to be working for us.
Found somithing about disabling the new UI but the option is not available anymore. Even if I add the space key after creating a page from the template with the button it won't work.
So we cant create pages from template macro from withing a global template.
Deleted Account (Inactive)
added a comment - - edited We do have the same issue except we can't creaty new pages with the button in any space. So this seems not to be working for us.
Found somithing about disabling the new UI but the option is not available anymore. Even if I add the space key after creating a page from the template with the button it won't work.
So we cant create pages from template macro from withing a global template. I was the user that has resulted in this bug report.
Further to expected result*s, I don't think that the space key should be mandatory in order for the template dropdown to be enabled (which is how it's worked for the 2+yrs I have been confluence admin within the business). *I think space key should be an optional form field. This would improve UX, as well as fixing the problems that I have been having.
UX would be improved as anytime that you want to edit the macro within the template, you have to set the space key before the save button is enabled....so you have to set it, make what ever change to any of the macro's form fields, before then deleting it and saving....so it would speed the process up and be less of a pain.
it really feels like this was an existing bug for ages, as that validation makes no sense.
Any further questions / clarifications, let me know.
Thanks
Ben
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!