sub-issue
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 3
- Avg merge
- 7m
- Merged PRs (30d)
- 3
Description
What is the correct way to use sub-issue ?
Nothing appears in the UI even if i've checked the "use sub-issue" option,
so I've manually tried flow:dependant :Iss1625242740456; on https://spoggy-test13.solidcommunity.net/public/issuetracker/new%20tracker/state.ttl
but nothing more in the ui
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
Reproduce the issue at the linked tracker URL using the “use sub-issue” option and the shown flow:dependant syntax. Start by tracing how sub-issues are represented and rendered in the issue pane. Done means the documented sub-issue flow produces the expected relationship in the UI, with the behavior verified against the reported examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100