hhmi issueshttps://gitlab.coko.foundation/hhmi/hhmi/-/issues2024-03-27T23:22:30Zhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/360Unpublished questions are appearing when filtering2024-03-27T23:22:30ZLenszie VilfrancheUnpublished questions are appearing when filtering## Expected behaviour
When filtering questions under browse items, users should not see any unpublished questions
## Current behaviour
When filtering questions under the browse items tab, unpublished questions appear in the results. ...## Expected behaviour
When filtering questions under browse items, users should not see any unpublished questions
## Current behaviour
When filtering questions under the browse items tab, unpublished questions appear in the results.
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
1. see recording https://go.screenpal.com/watch/cZet2oV7L7d
## Testing environment
<!-- Required. Provide all the relevant below -->
* Username of the user who experienced the problem: Melissa
* URL where the problem occured: see recording
* Browser name and version: chrome
* User machine: Mac
## Error logs (if available)
<!-- Provide the server or client logs -->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
## QA Steps
[To be completed by Coko]
## Scheduling
<!-- Include any known dependencies and an initial estimation (in hours) for this implementation. -->
[To be completed by Coko]
* Dependencies: [provide issue numbers]
* Development estimate: [provide in hours]
<!-- Bug label is added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Dione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/359Duplicate names appearing in chat2024-03-27T23:17:03ZLenszie VilfrancheDuplicate names appearing in chat## Expected behaviour
When @ mentioning individuals in the production chat only one name should appear.
## Current behaviour
Duplicate names are appearing when @ mentioned in production chat.
## Steps to reproduce
<!-- Required. P...## Expected behaviour
When @ mentioning individuals in the production chat only one name should appear.
## Current behaviour
Duplicate names are appearing when @ mentioned in production chat.
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
![Screenshot_2024-03-27_at_7.50.47_AM](/uploads/f654ed54fbdd4e99cc2c6ab9794b190f/Screenshot_2024-03-27_at_7.50.47_AM.png)
## Testing environment
<!-- Required. Provide all the relevant below -->
* Username of the user who experienced the problem: Melissa
* URL where the problem occured: see screenshot
* Browser name and version: chrome
* User machine: Mac
## Error logs (if available)
<!-- Provide the server or client logs -->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
## QA Steps
[To be completed by Coko]
## Scheduling
<!-- Include any known dependencies and an initial estimation (in hours) for this implementation. -->
[To be completed by Coko]
* Dependencies: [provide issue numbers]
* Development estimate: [provide in hours]
<!-- Bug label is added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Dione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/356Single word search not working2024-03-28T11:15:51ZLenszie VilfrancheSingle word search not working## Expected behaviour
When you search for a word that is in a question, the question should appear in the search results.
## Current behaviour
The search for a single word in the item (question) is not working. In this example, I sear...## Expected behaviour
When you search for a word that is in a question, the question should appear in the search results.
## Current behaviour
The search for a single word in the item (question) is not working. In this example, I searched for "match" in the "browse" and "editor" dashboards and did not get the result of the item I was looking for. I found the item once I explored the by-item type under "browse item."
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
![Match_Single_Word_Search](/uploads/042475d68743b51f58fffe59b122c021/Match_Single_Word_Search.mp4)
## Testing environment
<!-- Required. Provide all the relevant below -->
* Username of the user who experienced the problem: Teshell
* URL where the problem occured: see screen recording
* Browser name and version: chrome
* User machine: Mac
## Error logs (if available)
<!-- Provide the server or client logs -->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
## QA Steps
[To be completed by Coko]
## Scheduling
<!-- Include any known dependencies and an initial estimation (in hours) for this implementation. -->
[To be completed by Coko]
* Dependencies: [provide issue numbers]
* Development estimate: [provide in hours]
<!-- Bug label is added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Maintenance 2Sidorela UkuSidorela Ukuhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/355Search by author not working in Browse Items2024-03-25T14:05:26ZLenszie VilfrancheSearch by author not working in Browse Items## Expected behaviour
When saerching in the "Browse Items" tab. A user should be able to search by the author's name.
## Current behaviour
When you search by an authors name. No results appear.
## Steps to reproduce
<!-- Required....## Expected behaviour
When saerching in the "Browse Items" tab. A user should be able to search by the author's name.
## Current behaviour
When you search by an authors name. No results appear.
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
1. https://go.screenpal.com/watch/cZe3F2V7pEi
## Testing environment
* Username of the user who experienced the problem: Melissa
* URL where the problem occurred: https://assessment.biointeractive.org/discover
* Browser name and version: chrome
* User machine: Mac
## Error logs (if available)
<!-- Provide the server or client logs -->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
## QA Steps
[To be completed by Coko]
## Scheduling
<!-- Include any known dependencies and an initial estimation (in hours) for this implementation. -->
[To be completed by Coko]
* Dependencies: [provide issue numbers]
* Development estimate: [provide in hours]
<!-- Bug label is added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Sidorela UkuSidorela Ukuhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/354Cannot download more than one item in QTI format from within list2024-03-22T08:40:20ZDione Mentisdione@coko.foundationCannot download more than one item in QTI format from within list## Expected behaviour
<!-- Required. Tell us what should happen. Link to docs if possible. -->
Users should be able to select one, many, or all items in a list and download these in QTI format
## Current behaviour
<!-- Required. Tell...## Expected behaviour
<!-- Required. Tell us what should happen. Link to docs if possible. -->
Users should be able to select one, many, or all items in a list and download these in QTI format
## Current behaviour
<!-- Required. Tell us what happens instead of the expected behaviour. -->
This action does not work from within a list
(Workaround until this is fixed: download from the all lists page)
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
1. open a list, for example [here](https://hhmi.cloud68.co/list/18ae45a6-853c-4cb5-9205-038e46db6e84)
2. Select all or more than one
3. Select Epxort --> QTI
4. No error is shown and the action does not work
## Testing environment
<!-- Required. Provide all the relevant below -->
* Username of the user who experienced the problem:
* URL where the problem occurred:
* Browser name and version:
* User's machine: PC / Mac
## Error logs (if available)
<!-- Provide the server or client logs -->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
## QA Steps
[To be completed by Coko]
## Scheduling
<!-- Include any known dependencies and an initial estimation (in hours) for this implementation. -->
[To be completed by Coko]
* Dependencies: [provide issue numbers]
* Development estimate: [provide in hours]
<!-- Bug label is added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Maintenance 2https://gitlab.coko.foundation/hhmi/hhmi/-/issues/353Searching keywords that are more than one word2024-03-22T08:40:53ZDione Mentisdione@coko.foundationSearching keywords that are more than one word
## Expected behavior
On the discover page search input field you should be able to search based on keywords of the questions.
## Current behavior
Searching for keywords that are more than one word like for example `cell cycle`, shoul...
## Expected behavior
On the discover page search input field you should be able to search based on keywords of the questions.
## Current behavior
Searching for keywords that are more than one word like for example `cell cycle`, should give as result the questions with this keyword, but instead this returns 0 results.
## Steps to reproduce
In the testing site search for `cell cycle`, it should return at list this [question](https://hhmi.cloud68.co/question/442f219d-187f-4733-888b-7f1694e8c565/test)
1. Go to Browse items tab
2. Search for keywords that are more than one word long
3. See the result
Or
1. Create a new question
2. Add a double word keyword, for example `keyword one`
3. Publish the question
4. Go to Browse items and search for `keyword one`
## Testing environment
<!-- Required. Provide all the relevant below -->
* Username of the user who experienced the problem:
* URL where the problem occured:
* Browser name and version:
* User machine: PC / Mac
## Error logs (if available)
<!-- Provide the server or client logs -->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
## QA Steps
[To be completed by Coko]
## Scheduling
<!-- Include any known dependencies and an initial estimation (in hours) for this implementation. -->
[To be completed by Coko]
* Dependencies: [provide issue numbers]
* Development estimate: [provide in hours]
<!-- Bug label is added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Maintenance 2https://gitlab.coko.foundation/hhmi/hhmi/-/issues/352Error on Word export for specific question2024-03-20T09:45:54ZDione Mentisdione@coko.foundationError on Word export for specific question
## Expected behaviour
<!-- Required. Tell us what should happen. Link to docs if possible. -->
User should be able to export any item to word
## Current behaviour
<!-- Required. Tell us what happens instead of the expected behaviour...
## Expected behaviour
<!-- Required. Tell us what should happen. Link to docs if possible. -->
User should be able to export any item to word
## Current behaviour
<!-- Required. Tell us what happens instead of the expected behaviour. -->
Specific item results in error
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
1. Do to question: https://hhmi.cloud68.co/question/f7325caf-f53e-40fa-8a49-4366169af85f
2. Export to Word
3. See error
![Screenshot_2024-03-20_at_11.43.29](/uploads/4ec3cd66d6a46dbc374554e5f24033f0/Screenshot_2024-03-20_at_11.43.29.png)
## Testing environment
<!-- Required. Provide all the relevant below -->
* Username of the user who experienced the problem: Managing Editor (Dione)
* URL where the problem occurred: https://hhmi.cloud68.co/
## Error logs (if available)
<!-- Provide the server or client logs -->
Error in console:
```
ApolloError: Error: WaxToDocxConverter: RangeError: Invalid array length
at new t (main.8de8348d.js:2:7509438)
at main.8de8348d.js:2:7554117
at n (main.8de8348d.js:2:7658288)
at main.8de8348d.js:2:7658213
at new Promise (<anonymous>)
at Object.then (main.8de8348d.js:2:7658179)
at Object.next (main.8de8348d.js:2:7658298)
at y (main.8de8348d.js:2:7701495)
at b (main.8de8348d.js:2:7702001)
at t.next (main.8de8348d.js:2:7702534)
```
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
* Update Word converter
* Write relevant unit test
* Improve error message in UI if possible
## QA Steps
[To be completed by Coko]
## Scheduling
<!-- Include any known dependencies and an initial estimation (in hours) for this implementation. -->
[To be completed by Coko]
* Dependencies: [provide issue numbers]
* Development estimate: [provide in hours]
<!-- Bug label is added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Maintenance 2Grigor MaloGrigor Malohttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/351Navigate new users to their profile page during first login to AB site2024-03-19T13:54:46ZLenszie VilfrancheNavigate new users to their profile page during first login to AB site## Context
When new users log in to the AB site for the first time, we want them to be pushed to their profile page first to update their information.
## Proposal
When a user goes through the SSO process to log in, instead of being p...## Context
When new users log in to the AB site for the first time, we want them to be pushed to their profile page first to update their information.
## Proposal
When a user goes through the SSO process to log in, instead of being pushed to the homepage during their first login. They are pushed to their profile page.
## Design
![Screen_Recording_2024-03-18_at_4.41.28_PM](/uploads/c1440106707816524c96306c9ed07aa0/Screen_Recording_2024-03-18_at_4.41.28_PM.mov)
* apologies for the noise during the voice over
## Implementation (if applicable)
<!-- A description of the steps to implement the feature.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
<!-- Select the relevant option-->
- [ ] This feature is requested for the Phase 2
- [ ] This feature is requested for future enhanced versionsDione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/350Unable to export questions2024-03-19T14:06:46ZLenszie VilfrancheUnable to export questions## Expected behaviour
Users should be able to select questions and export them.
## Current behaviour
When a user attempts to export items saved in the "My List" tab, the functionality is not working. The user selects an item (or mult...## Expected behaviour
Users should be able to select questions and export them.
## Current behaviour
When a user attempts to export items saved in the "My List" tab, the functionality is not working. The user selects an item (or multiple items), and the options at the bottom of the page to "export" or "remove from the list" begin to blink. After trying for some time, the page crashes and gives an error code. Also, when I choose the "select all" option, only 1 item is selected instead of all items.
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
1. screen record:
![Recording__5_My_List_Export](/uploads/758c52ba65d0319f8971408bd6387d8f/Recording__5_My_List_Export.mp4)
2. Screenshot:
![image](/uploads/b49f91a8b52206506aa7362f519d4f5f/image.png)
## Testing environment
<!-- Required. Provide all the relevant below -->
* Username of the user who experienced the problem: Teshell
* URL where the problem occured: see screen recording
* Browser name and version: chrome
* User machine: Mac
## Error logs (if available)
<!-- Provide the server or client logs -->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
## QA Steps
[To be completed by Coko]
## Scheduling
<!-- Include any known dependencies and an initial estimation (in hours) for this implementation. -->
[To be completed by Coko]
* Dependencies: [provide issue numbers]
* Development estimate: [provide in hours]
<!-- Bug label is added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Maintenance 2Sidorela UkuGrigor MaloSidorela Ukuhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/349Unable to add image to question2024-03-26T03:40:07ZLenszie VilfrancheUnable to add image to question## Expected behaviour
When editing a question in the pre-published phase we should be able to add an image.
## Current behaviour
When editing a question in the pre-published phase, we cannot add the image to the question. We get an e...## Expected behaviour
When editing a question in the pre-published phase we should be able to add an image.
## Current behaviour
When editing a question in the pre-published phase, we cannot add the image to the question. We get an error message that say it cannot read properties.
## Steps to reproduce
<!-- Required. Provide a link to a live example or screenshots, and the steps to reproduce this bug.]-->
1.Go to the question
2.Add an image
3. Click save
4.Error appears
## Testing environment
<!-- Required. Provide all the relevant below -->
* Username of the user who experienced the problem: Teshell
* URL where the problem occured:
* Browser name and version: chrome
* User machine: Mac
## Error logs (if available)
![image](/uploads/f4c6f2695f3c8bd36ef2b7c12a89c4b6/image.png)
![image](/uploads/c2a3635c6fc19ab6c5c13d604128a2ab/image.png)
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
## QA Steps
[To be completed by Coko]
## Scheduling
<!-- Include any known dependencies and an initial estimation (in hours) for this implementation. -->
[To be completed by Coko]
* Dependencies: [provide issue numbers]
* Development estimate: [provide in hours]
<!-- Bug label is added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Maintenance 2Dione Mentisdione@coko.foundationSidorela UkuDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/348TEXT CHANGE: True/False questions are missing capitalization2024-03-19T13:55:42ZLenszie VilfrancheTEXT CHANGE: True/False questions are missing capitalizationWhen in a True/False questions the "True/false" label next to the toggle is missing a capitalized "f"
![Screenshot_2024-03-14_at_5.06.43_PM](/uploads/7534b08a273fb2f353f04baf25cef252/Screenshot_2024-03-14_at_5.06.43_PM.png)
Please upd...When in a True/False questions the "True/false" label next to the toggle is missing a capitalized "f"
![Screenshot_2024-03-14_at_5.06.43_PM](/uploads/7534b08a273fb2f353f04baf25cef252/Screenshot_2024-03-14_at_5.06.43_PM.png)
Please update this to display as True/FalseMaintenance 2Dione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/327Users are handling editors are not seeing assigned questions2024-01-12T19:46:52ZLenszie VilfrancheUsers are handling editors are not seeing assigned questions## Expected behaviour
When a handling editor is assigned a question, they should be able to view that the question is now assigned to them on their end.
## Current behaviour
When a handling editor is assigned a question, the question...## Expected behaviour
When a handling editor is assigned a question, they should be able to view that the question is now assigned to them on their end.
## Current behaviour
When a handling editor is assigned a question, the question does not appear on their end.
## Steps to reproduce
1. Assign a question to a handling editor
2. Sign in as the handling editor that is assigned the question
3. The question does not appear in the HE's view.
4. But the admin can see that the question is assigned
## Testing environment
* Username of the user who experienced the problem: mayvalerie@gmail.com
* URL where the problem occured: [see video](https://screenpal.com/watch/c0l2FNVmSRf)
* Screenshot of an example question:
![image](/uploads/81eea8d3c17ac00a7f52f6aa82915149/image.png)
## Error logs (if available)
<!-- Provide the server or client logs -->
## Possible solution
<!-- If known, provide details on how to fix the bug.-->
## QA Steps
[To be completed by Coko]
## Scheduling
<!-- Include any known dependencies and an initial estimation (in hours) for this implementation. -->
[To be completed by Coko]
* Dependencies: [provide issue numbers]
* Development estimate: [provide in hours]
<!-- Bug label is added automatically. After creating this issue you can link other related or blocking issues with the Gitlab's Linked issues functionality. -->Dione Mentisdione@coko.foundationLenszie VilfrancheTeshell Ponteen GreeneDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/325Add hidden "Description" field to images2024-03-18T11:11:51ZBridget ConneelyAdd hidden "Description" field to images<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, ...<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, and goals? -->
When there is an image in an assessment item, alt text will be available for screen readers, but there is a character limit to the amount of alt text that will be provided. We would like to add an optional description field to provide longer text for screen readers.
## Proposal
<!-- A precise statement of the proposed feature. -->
A new "description" field for images that is only available to screen readers after reading alt text.
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature -->
## Implementation (if applicable)
<!-- A description of the steps to implement the feature.-->
WAI advice for complex images: https://www.w3.org/WAI/tutorials/images/complex/
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
<!-- Select the relevant option-->
- [ ] This feature is requested for the Phase 2
- [x] This feature is requested for future enhanced versionsphase 3Vukile LangaDione Mentisdione@coko.foundationVukile Langahttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/318Global private chat for Editors2024-03-15T09:55:38ZDione Mentisdione@coko.foundationGlobal private chat for Editors<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, ...<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, and goals? -->
This idea came up in a meeting with HHMI on 30 Nov. Currently, the Assessment Builder workflows allow for three chat scenarios:
1. Chat between the editors and the author of an item
2. Chat between the editors and the reviewer of a item during the "In review" stage
3. Chat between the editors and the production team working on the item during the "In production" stage
There is no private (in-app) chat for the editors.
## Proposal
<!-- A precise statement of the proposed feature. -->
### Use cases
1. As a managing editor, sometimes I need to discuss work load or upcoming availability with handling editors before assigning items to them.
2. As a managing editor, sometimes I need to discuss the reviewers who may be invited to review items with the handling editors.
HHMI's preference id for the chat to be a global, meaning all MEs and HEs have access to one chat space, independent of the items. This works well when discussion need to happen about many items at one time.
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature -->
## Implementation (if applicable)
<!-- A description of the steps to implement the feature.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
<!-- Select the relevant option-->
This feature is requested for future enhanced versionsDione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/317report a bug from the app2024-03-15T09:55:41ZDione Mentisdione@coko.foundationreport a bug from the app<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, ...<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, and goals? -->
* Software maintenance teams require detailed bug reports to resolve issues on production deployments in good time.
* Most users are not experienced with providing the necessary information / They don't know what to provide unless the are prompted for the specifics.
* Often the client (HHMI) does not have a direct relationship with the user so it can be difficult or time consuming to get the necessary information.
## Proposal
<!-- A precise statement of the proposed feature. -->
* Provide a "report a bug" feature that collects the necessary information in a form
* Email the form content to a specified email (e.g. the instance's hosting org support email)
* Additionally, automatically create a Bug Issue in the relevant Coko Gitlab project.
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature -->
## Implementation (if applicable)
<!-- A description of the steps to implement the feature.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
<!-- Select the relevant option-->
This feature is requested for future enhanced versionsDione Mentisdione@coko.foundationDione Mentisdione@coko.foundationhttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/316Attribute an item to being associated with primary literature/source2024-01-18T12:03:56ZDione Mentisdione@coko.foundationAttribute an item to being associated with primary literature/sourcehttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/308Report issue with published item2024-03-18T11:09:58ZDione Mentisdione@coko.foundationReport issue with published item<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, ...<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, and goals? -->
Users should be able to report an issue with a published item. This idea came up in the discussion of #287 and HHMI asked for a proposal on 15 Nov.
## Proposal
<!-- A precise statement of the proposed feature. -->
* Add a 'report issue' flag icon on all published items (on individual items accessed from Browse Items page)
* Selecting the flag opens a modal for the user to report an issue
* "Report issue" action sends an email to the Assessment Builder users with an Admin role.
### Email text
[Subject] HHMI BioInteractive Assessment Builder: Reported issue with published item
[body]
`{Username/A user}` with email address `{email}` has reported an issue with a published item.
`{text and file uploads submitted in the Assessment Builder}`
Click on [this link](url) to view the item. If you cannot see the link, copy and paste the following link into your browser.
`{url for the item}`
[/end]
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature -->
Report issue icon
![HHMI_rough_wireframes_-_Report_issue__published_item](/uploads/f7670f86277a7c72edbfe591e69e0ebf/HHMI_rough_wireframes_-_Report_issue__published_item.jpeg)
Report issue modal for logged in user
![HHMI_rough_wireframes_-_Report_issue_modal_for_logged_in_user](/uploads/da874b5d2513b7093d7f59887f07c001/HHMI_rough_wireframes_-_Report_issue_modal_for_logged_in_user.jpeg)
## Implementation (if applicable)
<!-- A description of the steps to implement the feature.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
<!-- Select the relevant option-->
- [ ] This feature is requested for the Phase 2
- [x] This feature is requested for future enhanced versionsphase 3Vukile LangaVukile Langahttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/289Archive and show/hide items2024-03-27T05:50:02ZDione Mentisdione@coko.foundationArchive and show/hide items<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, ...<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, and goals? -->
HHMI requested we scope this feature in our PM meeting on 24 Oct.
**Use case**
There are multiple cases when users may want to archive items that they no longer need to see in the Dashboard. I archive an item when I'm done with it/there is no further action needed from me, but I still want to have a record of it.
As an author I have a list of questions that:
* have not been accepted by Editors (status = rejected)
* have been submitted by me (status = submitted)
* have been unpublished by Editors (status = unpublished)
* have been published (status = published, and I can see these on the Browse Items page)
As an editor (ME and HE) I have a list of questions that:
* have been unpublished and will not be published again (status = unpublished) (see new feature in #287)
* have been rejected and won't go any further in the flow (status = rejected)
* have been published (status = published, and I can see these on the Browse Items page)
As an Admin I have a list of questions that:
* have been published (status = published, and I can see these on the Browse Items page)
* have been unpublished and will not be published again (status = unpublished)
## Proposal
![HHMI_User_Flows_-_Archive](/uploads/8758696c5be3be20d4f5ee2d1574c47f/HHMI_User_Flows_-_Archive.jpeg)
### Archive
* Archiving items removes the item from the **user's dash** and applies an "archived" label.
* User can choose to show archived items, and hide archived items again.
* User can unarchive items
* Archiving does not change the item status.
#### Applicable statuses
* Allow all users to Archive items in the following statuses:
* Published
* UnPublished
* Rejected
* Allow Authors to Archive *their* items in a "submitted" state
## Design
<details><summary>Click to expand</summary>
Label on item row
![image](/uploads/43f7964ae6609900b6ef4c5c1058129f/image.png)
Archive / Unarchive action
![HHMI_rough_wireframes_-_Archive_Unarchive](/uploads/8b841d215e29f31912c64b233de109fe/HHMI_rough_wireframes_-_Archive_Unarchive.jpeg)
Confirmation modals
![HHMI_rough_wireframes_-_Archive_and_Unarchive_confirmation](/uploads/1bfbe2d7d8114e93fe835ac43fbe0968/HHMI_rough_wireframes_-_Archive_and_Unarchive_confirmation.jpeg)
</details>
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
Originally HHMI requested delete functionality but after reviewing the use cases we agreed hiding or archiving the items is better because there may be a reason in the future to use these items again.
## Scheduling
<!-- Select the relevant option-->
This feature is requested for the Phase 2phase 3Vukile LangaVukile Langahttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/267Draft: Enhance Search for Users Option for Admins When Managing Teams2024-01-18T12:11:40ZNatasha BuddDraft: Enhance Search for Users Option for Admins When Managing Teams<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, ...<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, and goals? -->
As an Admin responsible for managing teams on the Assessment Builder, the current search functionality is limited to searching for active users by User Name. However, in certain scenarios, a user may have multiple user accounts, making it challenging to identify the correct user. To enhance usability and accuracy, we propose expanding the search criteria to include filtering by email address.
## Proposal
<!-- A precise statement of the proposed feature. -->
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature -->
## Implementation (if applicable)
<!-- A description of the steps to implement the feature.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
<!-- Select the relevant option-->
- [ ] This feature is requested for the Phase 2
- [ ] This feature is requested for future enhanced versionshttps://gitlab.coko.foundation/hhmi/hhmi/-/issues/266Draft: Rearrange Order of Editor Action Tabs for Question Management2024-01-18T12:12:35ZNatasha BuddDraft: Rearrange Order of Editor Action Tabs for Question Management<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, ...<!-- Required. Provide a general summary of the issue in the title above -->
## Context
<!-- Give the necessary context for your proposal. For example, what problem will this feature solve for users? What are the use cases, benefits, and goals? -->
The current order of action tabs for Editors when managing questions lack a logical workflow. We need to rearrange these tabs to improve efficiency and usability.
## Proposal
<!-- A precise statement of the proposed feature. -->
Current Order:
1. Export to Word
2. Assign to HE
3. Do not accept
4. Move to Review
Desired Order:
1. Change style of the the "Export to Word" button to a secondary button (do not change its position)
2. Do not accept
3. Move to Review
4. Assign to HE
## Design
<!-- Include sketches or wireframes of the UI suggested for this feature -->
## Implementation (if applicable)
<!-- A description of the steps to implement the feature.-->
## Alternative approaches (if applicable)
<!-- Include any alternatives to meet this use case. -->
## Scheduling
<!-- Select the relevant option-->
- [ ] This feature is requested for the Phase 2
- [ ] This feature is requested for future enhanced versions