Due to the complex nature of overlap and conflict between items of development within a typical Salesforce implementation, there are significant challenges with managing version control of deployed components. The purpose of this document is to outline our agreed strategy for management of sandbox instances and our deployment cycle from development, through client testing and finally, production releases.
...
Jira items can be categorised into various issue types for ease of reporting, filtering, assignment and management of workflows. The issue types included in our Jira workflows are defined below;
Epics major development streams that can encompass various components and elements and can be shared across projects and boards
Can contain many stories, tasks and sub-tasks
Bugs are errors, faults or defects in components where expected behaviour is not observed
This issue type is automatically moved to the
Selected for Developmentstatus and prioritised (according to SLA)
Stories issue types are most often utilised for user stories provided by clients or gleaned from requirements gathering workshops
Used to document requirements or requests from clients
Can contain many tasks and sub-tasks
Not usually assigned to developers directly
Tasks and sub-tasks used for technical definitions of development work, usually created, written and managed by the consultancy and technical teams
Usually contain technical specifications translated from requirements
Used for development resource planning and estimates
...