A separate project for Fluid Engage in Jira

Victoria Moulder vmoulder at sfu.ca
Mon Aug 24 16:15:23 UTC 2009

Hi Justin,

Having separate channels for viewing Fluid Engaged and Infusion tasks in Jira would be more efficient!  

Leaving all Infusion tasks related to Infusion in their current location, and migrating the Fluid Engaged task to a channel named "Engaged" sounds good.  

My only suggestion would be that the folks who created the "Engaged" tasks, be responsible for closing them out and moving them to the new location - so that any errors or omissions could be avoided?

Best, Vicki 


----- Original Message -----
From: "Justin Obara" <justin.obara at utoronto.ca>
To: "fluid-work List" <fluid-work at fluidproject.org>
Sent: Friday, 21 August, 2009 18:08:59 GMT -08:00 US/Canada Pacific
Subject: A separate project for Fluid Engage in Jira


We are edging ever closer to releasing Infusion 1.2 and Engage 0.1.  
Currently we are using the same jira project to house the tasks/issues  
for both of these projects.

I propose that we should create a new project for engage, while  
leaving the current one "Fluid" for the Infusion line.

This will allow us to keep these lines separate, allowing for easier  
tracking of and reduce confusion that may be caused especially when it  
comes to version numbering in Jira.

The down side is that we will have to remember to keep track of two  
projects. That means filing jiras and committing with the correct one.  
There will undoubtedly be some mistakes made along the way.

Creating the new space will require a couple of things. First, we will  
have to move all of the current engage related jiras to the new space.  
Michelle has looked into this and it appears that we should be able to  
do a bulk move of the necessary jiras. Secondly we will have to create  
a new project key. The Project key is what is displayed in front of  
the issue number, and should be both short and meaningful. For example  
we currently see something such as FLUID-111. One suggestion would be  
to use Engage. That would look something like this Engage-111.

Please let me know what you think of this idea to create another Jira  
project for Fluid Engage and any suggestions for the project key.

fluid-work mailing list - fluid-work at fluidproject.org
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

More information about the fluid-work mailing list