-
Suggestion
-
Resolution: Unresolved
-
10
-
8
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
Right now when you add a Create from template macro in a Confluence page you have to pre-configure on which space the page will be created, but there are some situations where asking on which space or parent page will that page be created when the macro is clicked on is a more desirable behavior.
Take as an example a page from a Global Template which has the Create from template macro: once that page get's created the macro still points to the space that was defined on the Global Template, it would make more sense if you could choose the space and parent page where the page will be created (without having to go in and edit the macro each time you create a page from a template or moving the created page afterwards) or the macro should assume that the page should be created on the current space.
- is related to
-
- Gathering Interest
-
ACE-2908 You do not have permission to view this issue
- relates to
-
- Closed
-
- Gathering Interest
[CONFCLOUD-29581] Create from template macro should ask on which location the page will be created
Hello everyone,
We are currently shifting the efforts from templates to additional customization options for Confluence Cloud.
While we will not be closing this suggestion, this means that we will be pausing the implementation for new features related to templates, but will keep the maintenance and continue to fix bugs that have higher priorities as per our Bug Fixing Policy.
Thank you for your understanding.
Wish you the best,
Giuliano C.
Atlassian Team
All comments
Hi Anshuman,
I can see that the Create From Template Pro is currently free. Can K15t guarantee that this plugin will always remain free or will this change to a paid subscription? As long term customers of Atlassian, we've installed free plugins only for companies to trap us into paying for a subscription years down the line. For customers who don't know this happens, Atlassian doesn't really make it clear that 3rd party companies can change their plan at any time. I understand why they do it, but it puts Atlassian customers in a very difficult situation.
I agree with adding more parameters to the macro. I constantly need to add the page title like this for example - and people just DON'T PAY ATTENTION
[Page Title] - [YOUR NAME]
When creating Content Template, we can use Variables when building confluence templates which help users to do less manual lifting when creating pages, I would think that we can convert those variables from $fullname to be used on the front end.
Additionally, if you use the "insert page" macro, you can use variables - if you can use them there, why not on the Create From Template?
Sure this is Adaptavist Genius work, but if they can do it, why is it so hard for Confluence team do to this? Seems like with the number of related requests, this is something people are screaming for based on the number of votes on Create from Template enhancement requests.
The following parameters requested have been gathered a list of requests from CONFSERVER-33098:
Most Requested: parent page
- firstlast name
- currentweek
- currentweekday{{}}
- currentyear
- currentmonth
- currentday
- parentTitle
- tags
- specifying location of resulting page
- more parameters in the Title
- adding labels; set or variable "%"
- prefix + postfix
- prompt window to allow injection of custom text into the title.
The following Issues were gathered using the following Filter Query and shows exactly how many people are requesting enhancements to this Macro. (Total Votes: 1248){}
- https://jira.atlassian.com/browse/CONFCLOUD-33098 (217 votes)
- https://jira.atlassian.com/browse/CONFSERVER-33098 (259 votes) - on *SERVER *project.
- https://jira.atlassian.com/browse/CONFCLOUD-75346 (3 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-42814 (1 vote)
- https://jira.atlassian.com/browse/CONFCLOUD-66313 (32 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-30716 (109 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-65151 (0 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-40819 (4 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-29581 (64 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-77143 (0 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-54587 (2 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-74227 (1 vote)
- https://jira.atlassian.com/browse/CONFCLOUD-38208 (1 vote)
- https://jira.atlassian.com/browse/CONFCLOUD-40821 (0 vote)
- https://jira.atlassian.com/browse/CONFCLOUD-54839 (8 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-33006 (2 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-41265 (1 vote)
- https://jira.atlassian.com/browse/CONFCLOUD-46449 (0 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-66201 (1 vote)
- https://jira.atlassian.com/browse/CONFCLOUD-37713 (1 vote)
- https://jira.atlassian.com/browse/CONFCLOUD-32997 (25 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-35793 (0 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-31251 (8 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-75264 (5 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-37513 (123 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-63080 (31 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-3697 (71 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-13715 (16 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-45607 (108 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-75043 (5 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-40591 (5 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-32550 (2 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-71788 (0 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-29162 (26 votes)
- https://jira.atlassian.com/browse/CONFCLOUD-22704 (116 votes)
Hello everyone,
We are currently shifting the efforts from templates to additional customization options for Confluence Cloud.
While we will not be closing this suggestion, this means that we will be pausing the implementation for new features related to templates, but will keep the maintenance and continue to fix bugs that have higher priorities as per our Bug Fixing Policy.
Thank you for your understanding.
Wish you the best,
Giuliano C.
Atlassian Team
That sounds perfect, thanks!
Although, maybe it's not rolled out yet? I'm on version 3.1.0 and can't see any update yet, parent page is still a required field ...
Hey Andy,
Thank you for your feedback and kind words!
Just wanted to let you know that with the latest release of Create From Template Pro, you do not need to set the space and page any more.
This means that you no longer need to manually edit the macro on the parent page template after publishing. By configuring the macro on the template page, the parent page will automatically be set as the created page (that has the macro).
Cheers!
Thanks for the great work at K15t and bringing attention to this alternative 
Being able to add template parameters to the page title is very useful.
However, the create from template pro macro has the same problem - when adding the create from template pro macro to a template page, you still need to specify the parent page, so it's not possible to have a template that always creates pages as children of itself. Ideally there would be an option for the parent page to always be the page that had the create from template button.
If users can always remember to edit the 'create from template pro' macro on the parent page template after publishing, to set itself as the parent page, then this works ok.
Hey folks!
We, at K15t, also felt the need for these additional parameters in the Create From Template macro (one of our most used Confluence macros). So we built a Forge Macro - Create From Template Pro, back in 2021 for Atlassian Codegeist.
You can find it readily available on the Atlassian Marketplace, and the best part? It's completely free!
With the app, you can -
-
- Select the parent page
- Add additional labels
- Additional parameters for the page title
- Templatize the page title, and
- Specify basic styling for the button
I hope this helps with your use case.
Cheers!
I've found a few old threads like this after hitting this limitation myself ... would love to be able to use the create from template macro on the global templates but without the ability to default to using the current space this is useless.
Example use case, where we have a separate space for each project:
- Default space content has an 'Add project checklists' button which creates a page using the project checklists template.
- Project checklists template has further buttons to 'Add security checklist', 'Add performance checklist' Add release checklist'
A couple of simple templates then gives a nice clean consistent structure across all of our project spaces, especially as the create from template macro allows for the page titles to be specified. We can end up with a page structure like this:
- Project space overview page
- Project checklists
- Space name - Security checklist
- Space name - Performance checklist
- Space name - Release checklist
- Project checklists
Right now, that's frustratingly close to being possible - not being able to leave the space key empty or set as @self/@spaceKey means all these pages you'd want to be created in the project space where the macro is used would be created away in some other meaningless space instead.
Regarding "Another option would be to make the Space Key field in the macro simply default to the current space, or accept something like @spaceKey." (first comment): that's my opinion as well. If the field does have to be mandatory, make it accept a placeholder. Otherwise, make it optional so that the button defaults to page creation in the current space. This would make the macro usable in templates without problems.
The truly frustrating thing is the documentation says the Create from Template defaults to the current space. It just doesn't actually do that.
We're not asking you to implement a new feature. We're asking you to implement the feature you already designed and documented.