ElementList functional ElementListCommon
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] Duedate that is urgent is highlighted
- [ ] Presenting correct title and service owner for service instances
- [ ] Presenting message-icon according to status of correspondence instance
- [ ] Correspondence has correct prefix
- [ ] Correspondence with required confirmation has correct prefix
- [ ] Not opend correspondence has title in bold style
- [ ] Download attachments on correspondence
- [ ] message header is grayed out for user who does not have signing right
- [ ] Not opened reportingservice has title in bold style
- [ ] Opened reportingservice has title in non-bold style
- [ ] Collaboration service should have an icon and no prefix
- [ ] Inform user that there are too many elements in inbox
- [ ] Verify Mark as Unread for correspondence service
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the ElementListCommon functional tests and the ElementList implementation they exercise. Work through each unchecked behavior in the issue, then run the relevant test suite; done means all listed ElementList and correspondence, reporting-service, collaboration, inbox, and attachment checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100