ivanjay205
Registered
Just curious how most people do this. My primary responsibility at work is not software development. but I have created a app through Quick Base for project management for our company that we use extensively. As such I frequently get requests for new features and bugs people find.
For new features I create a project for each one I choose to implement and put it in someday until ready to begin it so I only have 1-2 active at a time. That works well.
What about for bugs? I could make a project for each one for the steps to resolve but honestly that typically takes longer than fixing it and I dont need to plan it all out. I could create one project just to house all of the bugs vs cloud my next actions list. I use FacileThings and it allows kanban views on projects so I could put all of the bugs there.
Or I could leave them all as next actions and just put them under an area of responsibility for software development.
Advice on the best way to do this?
Thanks in advance!
For new features I create a project for each one I choose to implement and put it in someday until ready to begin it so I only have 1-2 active at a time. That works well.
What about for bugs? I could make a project for each one for the steps to resolve but honestly that typically takes longer than fixing it and I dont need to plan it all out. I could create one project just to house all of the bugs vs cloud my next actions list. I use FacileThings and it allows kanban views on projects so I could put all of the bugs there.
Or I could leave them all as next actions and just put them under an area of responsibility for software development.
Advice on the best way to do this?
Thanks in advance!