Add more statuses for tickets
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
Research direction
Start by locating how ticket statuses are defined and how .env configuration is loaded. Clarify whether additional statuses should be supplied as a comma-delimited environment value, then verify that configured statuses are recognized throughout ticket handling.
Written by the indexing model from the issue text.
Description
set by .env as a comma-delimmited list or?
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from linuxgoose/Inque
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
linuxgoose/Inque#6 ·
-
Set up docs page Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
linuxgoose/Inque#4 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
linuxgoose/Inque#3 ·
-
Add notes support Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
linuxgoose/Inque#2 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
linuxgoose/Inque#1 ·
All issues in linuxgoose/Inque
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100