Content
View differences
Updated by Gerrit B. over 3 years ago
**As** a project manager
**I want to** create work packages while writing the protocol
**so that** I do not have to save the protocol and change the page
Naturally a lot of tasks are brainstormed during meetings. Actually, most of them are. We're trying to use the OpenProject meeting module on a beamer/on a shared screen to guide our meetings. As soon as we want to create a task I have to save the protocol to either use the work package blob that can be inserted inside the protocol or change to the work package view via a second tab. This is annoying and team members start questioning why we are using the meetings module in the first place.
Before I tried the meetings module, I used a solution where I could just type like this:
* Person A
* Topic 1
* Topic 2
* #task new task that just came up during this meeting
* Topic 3
* Information that just came up
* #task another task with a #date 2022-04-02 and a #prio high
I realize that OpenProject is more complex, probably too complex and customizable to create work packages by text only. A solution could be to extend the already implemented # functionality.
Currently typing # in a meeting protocol spawns a dropdown to select existing work packages. How about this? At the top of the list there is an option "create new". Typing # and just pressing enter (with first option "new work package" pre-selected) spawns a floating default new work package pop up like these:
<figure class="image op-uc-figure" style="width:50%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/27639/content"></div></figure>
After saving the new WP, the title is shown behind the # so it's more visible to the team. Currently it's just showing the ID, for example like <mention class="mention" data-id="34951" data-type="work_package" data-text="#34951">#34951</mention>.
**Acceptance criteria**
* "Create new work package" is offered at the top of the dropdown menue after typing # in meeting minutes
* The work package creation dialog does not interrupt the meeting protocol view
**Nice to have**
* Work packages referenced by # show the title to increase visibility (team members can't move the mouse to check for the mouse over infotext when we're using the meeting module on a shared screen)
* Writing @somebody within meeting minutes offers the mention functionality (like in work package comments)
* Writing @@somebody instantly sends an email to the person, ignoring his personal notification settings. The email previews the paragraph and backlinks to the protocol.
Adding these three things would make the meeting module a thing that integrated well. As of now, we write stuff into it and after the meeting we manually enter the work packages because we don't want to break the meeting flow. This creates unnessescary follow up work and makes using the meeting module no fun for team members and project managers.
**Edit:**
Niels came up with an even better approach to solve this. Inserting it here for better visibility.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="https://rgw1.netways.de/saasdataop/community/attachment/file/42094/image.png?response-content-disposition=inline&AWSAccessKeyId=c98f3ee5-8ef0-40b7-ad68-90e396d26a90&Signature=JVoW89eaT1eEXupW5YysEgENvgs%3D&Expires=1676058777" alt="https://rgw1.netways.de/saasdataop/community/attachment/file/42094/image.png?response-content-disposition=inline&AWSAccessKeyId=c98f3ee5-8ef0-40b7-ad68-90e396d26a90&Signature=JVoW89eaT1eEXupW5YysEgENvgs%3D&Expires=1676058777"></div></figure>
**I want to** create work packages while writing the protocol
**so that** I do not have to save the protocol and change the page
Naturally a lot of tasks are brainstormed during meetings. Actually, most of them are. We're trying to use the OpenProject meeting module on a beamer/on a shared screen to guide our meetings. As soon as we want to create a task I have to save the protocol to either use the work package blob that can be inserted inside the protocol or change to the work package view via a second tab. This is annoying and team members start questioning why we are using the meetings module in the first place.
Before I tried the meetings module, I used a solution where I could just type like this:
* Person A
* Topic 1
* Topic 2
* #task new task that just came up during this meeting
* Topic 3
* Information that just came up
* #task another task with a #date 2022-04-02 and a #prio high
I realize that OpenProject is more complex, probably too complex and customizable to create work packages by text only. A solution could be to extend the already implemented # functionality.
Currently typing # in a meeting protocol spawns a dropdown to select existing work packages. How about this? At the top of the list there is an option "create new". Typing # and just pressing enter (with first option "new work package" pre-selected) spawns a floating default new work package pop up like these:
<figure class="image op-uc-figure" style="width:50%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/27639/content"></div></figure>
After saving the new WP, the title is shown behind the # so it's more visible to the team. Currently it's just showing the ID, for example like <mention class="mention" data-id="34951" data-type="work_package" data-text="#34951">#34951</mention>.
**Acceptance criteria**
* "Create new work package" is offered at the top of the dropdown menue after typing # in meeting minutes
* The work package creation dialog does not interrupt the meeting protocol view
**Nice to have**
* Work packages referenced by # show the title to increase visibility (team members can't move the mouse to check for the mouse over infotext when we're using the meeting module on a shared screen)
* Writing @somebody within meeting minutes offers the mention functionality (like in work package comments)
* Writing @@somebody instantly sends an email to the person, ignoring his personal notification settings. The email previews the paragraph and backlinks to the protocol.
Adding these three things would make the meeting module a thing that integrated well. As of now, we write stuff into it and after the meeting we manually enter the work packages because we don't want to break the meeting flow. This creates unnessescary follow up work and makes using the meeting module no fun for team members and project managers.
**Edit:**
Niels came up with an even better approach to solve this. Inserting it here for better visibility.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="https://rgw1.netways.de/saasdataop/community/attachment/file/42094/image.png?response-content-disposition=inline&AWSAccessKeyId=c98f3ee5-8ef0-40b7-ad68-90e396d26a90&Signature=JVoW89eaT1eEXupW5YysEgENvgs%3D&Expires=1676058777" alt="https://rgw1.netways.de/saasdataop/community/attachment/file/42094/image.png?response-content-disposition=inline&AWSAccessKeyId=c98f3ee5-8ef0-40b7-ad68-90e396d26a90&Signature=JVoW89eaT1eEXupW5YysEgENvgs%3D&Expires=1676058777"></div></figure>