Can blueprints be set to go to a predefined place in the tree?

[Deleted user]

I'd like to have bluerprints that once created, all go into the same place, making it easier for my users to add and find content.

An example:

In this case a HR employee adding minutes from the last meeting:

1. Go to HR space in confluence

2. Click 'Create'

3. Select Meeting Minutes blueprint

4. Fill in blueprint, click 'Save'.

5. Blueprint is automatically put into 'HR Space > Minutes > Meeting minutes 1/1/2000'

Please point me in the right direction if this is possible.

Many thanks.

[Sherif Mansour · Accepted solution]

I think you are after this feature request: https://jira.atlassian.com/browse/CONF-29499

[Ellen Feaheny [AppFusions]]

Nice add Sherif -

Voted!

Come on folks - vote 'er up!

[Ellen Feaheny [AppFusions]]

We could make a custom plugin for this - it would not be hard.

We did a very similar use case for a couple yrs ago, of meeting notes sorted automagically with date delimiters (also with the ability to email in the meeting notes, and land in the right place in Confluence, and structured properly).

Its very similar to the blueprint concept, with a twist.

Confluence cocktail? ;)

Ellen

info@appfusions.com

[Sherif Mansour]

More votes doesn't necessarly mean we implement the features! The voting systme is broken in many ways. But just watch the issue to stay updated.

[Paul Brown]

This is how the Blueprint for Product Requirements works today.

I would like the Blueprint for Product Requirements to create the index and group of requirements as a children of the current page the user is on when they initiate the Create > Product Requirement workflow the first time from that page.

Then when the Add Product Requirements is clicked within the requirement index page the requirement is added to that index page.

We do not have the ability to create Workspaces in our environment but can segregate our pages using the heirarchy.

The current design puts all requirements entered into only one index which is off of the Home page for the Workspace and will not create multiple Product Requirement index pages to manage separate collections of requirements.

A Home page requirements report of all requirements may be of benefit to some users for the bigger picture but I would like to capture specific requirements by grouping.

Thank you

Paul Brown

[Sherif Mansour]

I think we could solve this by this feature reuqest: https://jira.atlassian.com/browse/CONF-29499

Or keep it as one index page, but let you build filters out of them https://jira.atlassian.com/browse/CONF-29421

[Paul Brown]

Hi Sherif,

Instead of Or I would say And.

I figured out a work around by by placing a copy of the Home located index page below the Product page I wanted the detailed pages stored. Then I modified the view fiter of the sub-page index to use the prodreq keyword for the group and removed the filter for Requirements so only prodreq items are displayed.

Since I cannot define what keywords are assigned automatically when I run the Product Requirements Blueprint through the Add Product Requirement button on the product index page, I have to add the Keyword prodreq to each page I add.

Leaving the Requirements keyword in place provides the information on Home based master list as well.

The ability to filter the table on any column would be great to remove the completed or resolved requiremets so viewers could focus on what needs the most attention.

I have voted for both of these requests because I see value in specific components of each.

Thank you

Paul