Skip to content

Issues: kartoza/GEEST2

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.

Sign up for GitHub

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

73 Open 463 Closed
73 Open 463 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Linking PR to tickets
#838 opened Feb 4, 2025 by mvmaltitz
@mvmaltitz
Maintaining the kanban board so that we are organised in our work
#837 opened Feb 4, 2025 by mvmaltitz
@timlinux
Check in daily on work progress
#836 opened Feb 4, 2025 by mvmaltitz
@timlinux
Make regular builds for the client to use during development
#835 opened Feb 4, 2025 by mvmaltitz
@timlinux
Send client regular updates on technical progress
#834 opened Feb 4, 2025 by mvmaltitz
@timlinux
Working on tickets without sizes
#833 opened Feb 4, 2025 by mvmaltitz
@timlinux
Working on tickets where you have exceeded your hours
#832 opened Feb 4, 2025 by mvmaltitz
@timlinux
Working on items not on the board
#831 opened Feb 4, 2025 by mvmaltitz
@timlinux
Making 'desire' features
#830 opened Feb 4, 2025 by mvmaltitz
@timlinux
Persisting spaghetti code
#829 opened Feb 4, 2025 by mvmaltitz
@timlinux
Work in clearly defined sprints with clear deliverable goals for each sprint
#828 opened Feb 4, 2025 by mvmaltitz
@timlinux
Telling client when things are not possible or costly
#827 opened Feb 4, 2025 by mvmaltitz
@timlinux
Make sure the client is always aware of the budget if we are on a burn down
#826 opened Feb 4, 2025 by mvmaltitz
@timlinux
Involving client in the sprint planning
#825 opened Feb 4, 2025 by mvmaltitz
@timlinux
broadly plan the work up front and have a series of checkpoints that raise an alarm with the client early if we are going off the plan
#824 opened Feb 4, 2025 by mvmaltitz
@timlinux
write tests from the beginning
#823 opened Feb 4, 2025 by mvmaltitz
@timlinux
refactor code as we work to make it more efficient and maintainable
#822 opened Feb 4, 2025 by mvmaltitz
@timlinux
describing features to the client before we build them
#821 opened Feb 4, 2025 by mvmaltitz
@timlinux
Creating/updating tickets directly after a meeting
#820 opened Feb 4, 2025 by mvmaltitz
Daily stand up meetings and communication with project leads.
#819 opened Feb 4, 2025 by mvmaltitz
Specific sprint meeting about QGIS Documentation and QGIS Websites
#818 opened Feb 4, 2025 by mvmaltitz
Communicating blocked tickets and follow up on their updates
#817 opened Feb 4, 2025 by mvmaltitz
Keeping it short, brief and to the point
#816 opened Feb 4, 2025 by mvmaltitz
Mention the story points for the day
#815 opened Feb 4, 2025 by mvmaltitz
Set sprint goals
#814 opened Feb 4, 2025 by mvmaltitz
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.