You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
duker33 opened this issue
Jan 30, 2018
· 0 comments
Labels
1 hourtypical issue size. It's one pdd hour. Performer should spend about one astronomical hour for it3we can defer this issue. But it'll good to implement itdevtask about development. Some markup or codetake itany teammate can take this issue and start working with it
The text was updated successfully, but these errors were encountered:
duker33
added
1 hour
typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for it
2 hours
some big and monolith issues. For example with hard decisions or discussions
take it
any teammate can take this issue and start working with it
dev
task about development. Some markup or code
3
we can defer this issue. But it'll good to implement it
and removed
2 hours
some big and monolith issues. For example with hard decisions or discussions
labels
Mar 14, 2018
1 hourtypical issue size. It's one pdd hour. Performer should spend about one astronomical hour for it3we can defer this issue. But it'll good to implement itdevtask about development. Some markup or codetake itany teammate can take this issue and start working with it
Continuous integration
Check for success app building.
Example here:
https://github.com/fidals/shopelectro
The text was updated successfully, but these errors were encountered: