-
Notifications
You must be signed in to change notification settings - Fork 2
Issues: fidals/refarm-site
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Use docker .env file
3
we can defer this issue. But it'll good to implement it
30 mins
small issues. Usually cosmetic fixes
cleanup
everything that do project stronger, flexible, reusable
easy
new teammates can start with such issues to become familiar with project
wontpay
#94
by duker33
was closed Aug 7, 2018
Travis fails because of disabled recursive requirements intalling
wontfix
#8
by duker33
was closed Oct 23, 2017
Improve Admin UI
30 mins
small issues. Usually cosmetic fixes
#79
by duker33
was closed Feb 27, 2018
SE/STB/RF Write index.md with template
1 hour
typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i
1
burning issue
docs
issue for improving project's documentation. Tech writers can perform some of this issues
wontfix
#80
by duker33
was closed Jun 3, 2018
Refactor Search Arch
2 hours
some big and monolith issues. For example with hard decisions or discussions
tail
#85
by duker33
was closed Feb 27, 2018
Refactor models fields
15 mins
small issues. Usually cosmetic fixes
tail
#86
by duker33
was closed Feb 27, 2018
Research Selenium Grid
1 hour
typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i
tail
#91
by duker33
was closed Nov 2, 2017
Enable Postgres connection pool
1 hour
typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i
2
performer can implement issue at his closest convenient time
Cache
feature
easy
new teammates can start with such issues to become familiar with project
report
Put it to completed tasks temporary list for business
tail
#92
by duker33
was closed Jun 22, 2018
Create glossary
1 hour
typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i
1
burning issue
#100
by duker33
was closed Feb 27, 2018
Move docs from RST to MD
1 hour
typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i
1
burning issue
#102
by duker33
was closed Dec 22, 2017
Add .editorconfig. se2, stb2
2
performer can implement issue at his closest convenient time
15 mins
small issues. Usually cosmetic fixes
cleanup
everything that do project stronger, flexible, reusable
easy
new teammates can start with such issues to become familiar with project
report
Put it to completed tasks temporary list for business
#112
by duker33
was closed Jun 20, 2018
Docker stale images
3
we can defer this issue. But it'll good to implement it
30 mins
small issues. Usually cosmetic fixes
hard
issue requires strong architecture skills, management skills, project domain area, etc
wontfix
#115
by ArtemijRodionov
was closed Jun 4, 2018
test_views.py:20-21: Create fixtures for tests now we...
1 hour
typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i
1
burning issue
cleanup
everything that do project stronger, flexible, reusable
#118
by 0pdd
was closed May 22, 2018
Write readme with good template
1 hour
typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i
3
we can defer this issue. But it'll good to implement it
docs
issue for improving project's documentation. Tech writers can perform some of this issues
invalid
#120
by duker33
was closed May 11, 2018
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.