Sub-projects as components or versions/releases

[mburgess]

We are setting up agile for operations.  We have zero development people on our team.  The desire is to (at least start) use Scrum and potentially move to Kanban.

1. We are going to start out with weekly Sprints

2. We have already created custom issue types, screens, etc..

3. We are sticking to the Epic -> Story -> Sub-task for projects

4. We have another issue hierarchy for operations work and will plan a buffer

5. We only have ONE project in JIRA.  This "Project" is really our program and we want to manage all of our real projects under the Program.

So, right now I have Jira setup to track projects/sub-projects by components.  This seems to be working okay and I have some automation for parent/child issue creation.  I am concerned about tracking components (start-end dates, etc..).  

Do you recommend that I move my sub-projects over to versions/releases instead?  So, instead of having a component label assigned to an epic, story, and sub-task as the project name.  I would do that with the Affected Version field.

One benefit would be completing a release would signal completion of the project vs just archiving a component.

Pros/Cons?