lumodon / lumodon/Issue-Distributor
Link directly to backoffice
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
You can go directly to an issue with the following link IF you're logged in AND you don't have a backoffice tab open. Not the most common situation but still better than nothing.
We should update the issue numbers in our issue distributor to contain this link:
`https://icobo.cashbet.com/crm/#/crm/players/view/1025291?claimedIssueId=20617&tabId=player-1025291-20617&tabText=_zinnguyen2712vn_gmail_com`
This means we additionally need to capture the actorid and email from the issue fetch step, and create another migration to modify table to allow issues to have email and actorid as extra rows.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the issue fetch step and the issue distributor logic to trace how issue numbers are generated. Review the table schema and migration approach for storing actorid and email, then verify that generated issue links include the fetched values and preserve the specified backoffice URL format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100