Where would feature mapping fall give the details below for activity based tracking?

Fermin Aldea_u3l6pw

Issue Type	Use Cases
Development	All standard development work (i.e code changes, configuration changes, deployments) Code-related discussions and code review Solutions Architect design activities
Analysis	All standard BSA activities Requirements gathering
Project Management	All standard project manager activities Providing project estimates
Project Meeting	Agile ceremonies (daily scrum, backlog grooming, sprint planning) Status calls
Training	KT to resources related to a project Training meetings and training documentation

Bill Sheboy

Hi @Fermin Aldea  -- Welcome to the community!

What problem are you trying to solve?  

It seems like you are trying to compartmentalize the span of work for product development using issue types. If so, why?  Understanding the problem will help the community provide ideas for you to consider.

When I do feature mapping, it is normally a bridge between opportunity canvasing and product delivery, and so includes (but is not limited to): problem statement, workflow mapping, discovery, solution identification and selection (MVP), solution decomposition to MVPe, release planning, and risk/issue management.

If your organization is very structured, and has something like a Project Management Office (PMO), you may want to ask for their assistance.

Best regards,

Bill