Content
View differences
Updated by Dominic Bräunlein 3 days ago
### Concept # User Problem
A user can link existing wiki pages ## User
_What persona, persona segment, or create a new wiki page in XWiki directly from OpenProject by using quick commands in customer type experiences the work package toolbar. problem most acutely?_
### Acceptance criteria
In OpenProject:
* There are two new Macros in the work package toolbar
Project manager
* "New wiki page" and "Add wiki page"
<br>
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918299/content">
Project member
* A _New wiki page_ dialog will appear:
Product owner
* The user will be invited to enter a title for the Wiki.
Customer
* In ....
## Problem
_What problem or job does the future, they will also be able to select the Space to which this Wiki will belong.
user have?_
* The newly-created wiki page will appear in ...
* <br>
## Pain
_What is the Wiki tab since primary workaround that users perform that we could remove or replace? Why is it is also automatically linked with the work package.
painful?_
* If ....
* <br>
# Business Case
## Reach
_About how many users, customers or potential customers currently have this problem? (Low / Worst Case)_
> Add this value to the link was created in-line, custom field and delete this section.
## Impact
_Among relevant customers or prospects, how much value do they get from a corresponding link will appear. Clicking on comprehensive solution to this link will take the user problem? (Conservative case)_
> Add this value to the newly-created page on XWiki.
### Implementation custom field and delete this section.
* Prerequisites:
* (assumed ## Confidence
_What are the top risk factors that could inhibit our ability to be present) OpenProject's rich text editor has a generic slash-command UX pattern implemented, generically allowing "providers" deliver this solution? Please consider how we can mitigate these risks._
> Add this value to register commands (Currently not yet available. Implementation outside the scope custom field and delete this section.
## Urgency and Priority
_What is the relative priority of this here. Will be done by OpenProject independently)
* (assumed to be present) XWiki API for listing spaces
* (assumed to be present) XWiki API for listing pages, optionally filtering by space
* (Implementation needed opportunity in XWiki) XWiki API for pages that allow for creating your backlog? What tradeoffs must you make? Is there a link hard deadline or could this wait?_
> Add this value to a OpenProject work package
* (Implementation needed in XWiki the custom field and OpenProject) Bi-directional OAuth setup on administrator level. Defined delete this section.
## Solution
_How do we solve the user’s problem. What is our “pain killer”? What must we achieve in ##55601.
* Slash command editor macro "Create new wiki page"
* Effort:
* UI to guide the user first version of the solution in order to grant OpenProject access to XWiki via OAuth unless a valid access token is already present.
* Implement slash-command "provider" achieve value for **creating** wiki pages
the user?_
* Modal window with a form for creating a wiki page
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="https://community.openproject.org/api/v3/attachments/107263/content"></div></figure>
* Inputs
* Select target space
* Select target page
* Text field <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="https://community.openproject.org/api/v3/attachments/107264/content"></div></figure>
## Out of Scope for page title
* On form submit
* create page by sending a POST request to XWiki to create the page
* send POST request to XWiki to create MVC
_What should NOT be in the link between work package minimal viable change, and freshly created wiki page
can be considered for future iterations? Why? Please order them by importance._
* Show optional link "Edit page in XWiki"
* On modal close
* send POST request to XWiki to create ...
## Differentiation
_What do you believe will differentiate us from the link
current experience or competitive experiences?_
* update ...
## Next iteration
_What is the current work package "Wiki" tab next solution that would allow us to show new link
release meaningful customer value quickly?_
* Insert OpenProject rich text editor macro for showing a link to the wiki page.
### Visuals
**User cans type / ...
* <br>
# Launch and select** _**New wiki page**_ **to create and link a wiki page in-line:** Growth
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/107263/content"> ## Measures
**The New wiki page dialog lets users type a name and (in _How will you know you solved the future) select a space:** problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the solution?_
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/107264/content"> * ...
## Messaging
**The link also appears in _If you were to write a press release, how would you describe the Wikis tab in the right-hand split screen:** value to customers?_
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/107265/content"> <figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">First Paragraph</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Customer Quote</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr></tbody></table></figure>
### Mockups ## Go to market
**View early-stage mockups _How are you planning on Figma:**
### getting this into users&#39; hands?_
A user can link existing wiki pages
_What persona, persona segment,
### Acceptance criteria
In OpenProject:
* There are two new Macros in the work package toolbar
<br>
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/918299/content">
## Problem
_What problem or job does
* <br>
## Pain
_What is
* <br>
# Business Case
## Reach
_About how many users, customers or potential customers currently have this problem? (Low / Worst Case)_
> Add this value to
## Impact
_Among relevant customers or prospects, how much value do they get from
> Add this value
### Implementation
* Prerequisites:
* (assumed
_What are the top risk factors that could inhibit our ability
> Add this value
## Urgency and Priority
_What is the relative priority
* (assumed to be present) XWiki API for listing spaces
* (assumed to be present) XWiki API for listing pages, optionally filtering by space
* (Implementation needed
> Add this value
* (Implementation needed in XWiki
## Solution
_How do we solve the user’s problem. What is our “pain killer”? What must we achieve
* Slash command editor macro "Create new wiki page"
* Effort:
* UI to guide the user
* Implement slash-command "provider"
* Select target space
* Select target page
* Text field
## Out of Scope
* On form submit
* create page by sending a POST request to XWiki to create the page
* send POST request to XWiki to create
_What should NOT be in
* On modal close
* send POST request to XWiki to create
## Differentiation
_What do you believe will differentiate us from
## Next iteration
_What is
### Visuals
**User cans type /
* <br>
# Launch
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/107263/content">
**The New wiki page dialog lets users type a name and (in
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/107264/content">
## Messaging
**The link also appears in
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/107265/content">
### Mockups
**View early-stage mockups
###