Content
View differences
Updated by Dominic Bräunlein 3 days ago
# User Problem
## Problem User
* Keyword search only returns results when Project manager
* QA members
* <br>
* Customer
* ....
## Problem
_What problem or job does the user already knows how something was described. have?_
* ...
* Users can narrow results with filters, but that requires knowing the right project, version, or other criteria upfront. <br>
## Pain
_What is the primary workaround that users perform that we could remove or replace? Why is it painful?_
* **Duplicate work:** Feature requests and bug reports get created multiple times because contributors cannot verify whether the same issue already exists. ....
* **Lost decisions:** When implementing a feature <br>
# Business Case
## Reach
_About how many users, customers or investigating potential customers currently have this problem? (Low / Worst Case)_
> Add this value to the custom field and delete this section.
## Impact
_Among relevant customers or prospects, how much value do they get from a bug, developers comprehensive solution to this problem? (Conservative case)_
> Add this value to the custom field and product managers cannot easily find delete this section.
## Confidence
_What are the work packages top risk factors that explain why could inhibit our ability to deliver this solution? Please consider how we can mitigate these risks._
> Add this value to the custom field and delete this section.
## Urgency and Priority
_What is the relative priority of this opportunity in your backlog? What tradeoffs must you make? Is there a functionality works hard deadline or could this wait?_
> Add this value to the way it does.
* **Incomplete discovery:** Users researching a problem area cannot surface all related work packages unless they know every keyword custom field and synonym used across all contributors and projects.
# delete this section.
## Solution
_How do we solve the user’s problem. What is our “pain killer”? What must we achieve in the first version of the solution in order to achieve value for the user?_
* Notes:
* Use pgvector
* Use half-precision then up to 4000 dimensions are supported
* Dimension are configurable in the admin config
* The embeddings are saved in its own table
* Dimension size is optionally used for API calls to define dimension size
* On admin configuration the column is dropped and newly generated with index based on the configured size
* Admin configuration also needs a configureable prefix for search and document query
* Configurable batch count
* Should display progress on re-calculation of index
* Search UI should show when re-calculating
* Search could be limited to work packages first and be as small as a checkbox "Use semantic search"
* <br>
## Out of Scope for the MVC
_What should NOT be in the minimal viable change, and can be considered for future iterations? Why? Please order them by importance._
* Meetings, documents, projects, wiki ...
## Differentiation
_What do you believe will differentiate us from the current experience or competitive experiences?_
* ...
## Next iteration
_What is the next solution that would allow us to release meaningful customer value quickly?_
* ...
* <br>
# Launch and Growth
## Measures
* Measure _How will you know you solved the position of problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the work package the user was looking for within the search results
solution?_
* Measure how often it is used ...
## Messaging
<br> _If you were to write a press release, how would you describe the value to customers?_
<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">Search smarter, not harder.</p></td></tr><tr 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">Stop scanning filtered lists and guessing keywords. Semantic search understands the meaning behind your query and surfaces relevant work packages</p></td></tr><tr 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>
## Go to market
_How are you planning on getting this into users' hands?_
## Problem
* Keyword search only returns results when
* QA members
* <br>
* Customer
* ....
## Problem
_What problem or job does
* ...
* Users can narrow results with filters, but that requires knowing the right project, version, or other criteria upfront.
## Pain
* **Lost decisions:** When implementing a feature
# Business Case
## Reach
_About how many users, customers
> Add this value to the custom field and delete this section.
## Impact
_Among relevant customers or prospects, how much value do they get from
> Add this value to the custom field
## Confidence
_What are
> Add this value to the custom field and delete this section.
## Urgency and Priority
_What is the relative priority of this opportunity in your backlog? What tradeoffs must you make? Is there
> Add this value to
* **Incomplete discovery:** Users researching a problem area cannot surface all related work packages unless they know every keyword
#
##
* Use pgvector
* Use half-precision then up to 4000 dimensions are supported
* Dimension are configurable in the admin config
* The embeddings are saved in its own table
* Dimension size is optionally used for API calls to define dimension size
* On admin configuration the column is dropped and newly generated with index based on the configured size
* Admin configuration also needs a configureable prefix for search and document query
* Configurable batch count
* Should display progress on re-calculation of index
* Search UI should show when re-calculating
* Search could be limited to work packages first and be as small as a checkbox "Use semantic search"
* <br>
## Out of Scope for the MVC
_What do you believe will differentiate us from the current experience or competitive experiences?_
* ...
## Next iteration
_What is the next solution that would allow us to release meaningful customer value quickly?_
* ...
* <br>
## Measures
* Measure
## Messaging
<br>
<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">Search smarter, not harder.</p></td></tr><tr
## Go to market
_How are you planning on getting this into users' hands?_