Jump to content

Jira Question


Recommended Posts

I have looked at the two blog posts related to integrating with JIRA. One suggests branching per task, and one suggests branching per changeset. My question/observation is that with AGILE, you really need both.

I may have a User Story artifact that I want to create a branch for. When that branch is complete, I want to close that user story. This is similar to the Branch Per Task paradigm, except that User stories are usually very large and get decomposed into smaller Task artifacts. Each task usually corresponds to a changeset checkin. So I guess what I'm asking is, how can you support this hybrid approach in Plastic?


--UserStory1(Branch) [JIRA Item 1]

---Task1(changeset) [JIRA Item 2]

---Task2(changeset) [JIRA Item 3]

---Task3(changeset) [JIRA Item 4]

--UserStory2(Branch) [JIRA Item 5]

--Task4(changeset) [JIRA Item 6]

--Task5(changeset) [JIRA Item 7]



Link to comment
Share on other sites


You described the scenario pretty well, and using an interesting explanation of how an agile paradigm works... pretty cool.

Now, there's one thing I don't agree and it is the cset to task mapping. I guess it is a reminiscent of some other SCM (SVN, Perforce?). Let's see:

- the mapping with task per branch is that task3 won't be just a cset but a branch!

- Each task has a branch, not only big tasks (stories), that's the beauty of branch per task!!

Do you get the point now? Not just branches for big things (that's how svn or perforce tried to do it in the past), but a new branch for everything.

And, of course, not just a cset per task, even an small one can have more than one cset and hence they'll be grouped on a branch.

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...