Hey y'all,
Thanks for following this down the rabbit hole.
I don't think the effort to do JIRA scripting is warranted here. I
think we can focus on creating JIRAs for the currently-working-on
components now and can revisit older components as we need them. In
the next few months we'll be doing some integration work that will
allow us to revisit older components and also give us a chance to
(re)organize things in JIRA and get a feel for what it's like to
iterate through those phases again. We're bound to learn more about
how to organize ourselves while we do that integration work and
iterate on those framework phases.
So, though it might be the *right* thing to do technically, I'm gonna
say let's stick to what we have even though it's heinous since it's
finite and we've got a number of components already represented in JIRA.
Since this process is new to us and we're still working out the best
way to organize ourselves, I'd recommend we just focus on those
components we're working on now. And we can have some flexibility in
this since we aren't going to rely on the existence of all framework
JIRAs to do progress indication. So, perhaps we can focus on up-
coming JIRA tasks for components and when we have some moments
backfill the already worked on ones.
Best,
Jess
~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
[EMAIL PROTECTED]
/ w / 617.326.7753 / c / 919.599.5378
jabber: [EMAIL PROTECTED]
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~
On Sep 3, 2008, at 6:31 PM, Allison Bloodworth wrote:
Thanks so much for looking into this Gary! The subtasks issue isn't a
big deal for us with the Design Framework tasks as (at least
currently) there are no subtasks. However, it seems to me that
exploring #2 could save us a LOT of time. If we could just run a
script to create all the design tasks we'd need for a component it
would help a lot.
I'm sure we'll get faster as time goes on, but Daphne and I probably
took over an hour to enter all our tasks for Inline Edit and last
night it probably took me an *at least* an hour to enter all the
dependencies on them. In the end I found the only way to look at both
the Design Framework example tasks AND the Inline Edit tasks was to
have two browsers open because it appears shared cookies between tabs
will mess up your filters if you're using more than one. There are
also TONS of opportunities for error with this copying process (and
when you do screw up and make an error it takes even longer).
Should we enter a JIRA task for exploring the creation of a script to
create our tasks and dependencies? At a quick glance, there are a
couple examples on the Jelly reference from Gary
(http://www.atlassian.com/software/jira/docs/latest/jelly.html
) that I think may apply to what we are doing:
Create and assign issue
<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraTagLib">
<jira:CreateIssue project-key="TST" summary="My Issue summary"
issueKeyVar="keyvar"/>
<jira:AssignIssue key="${keyvar}" assignee="testuser"/>
</JiraJelly>
Create Issue and Comment
<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraTagLib">
<jira:CreateIssue project-key="TP" issueType="Bug" summary="Issue
summary" issueKeyVar="key"/>
<jira:AddComment issue-key="${key}" comment="A comment on ${key}"/>
</JiraJelly>
Cheers,
Allison
On Sep 3, 2008, at 9:24 AM, Gary Thompson wrote:
All,
I did some research on cloning JIRA issues with subtasks and the
possibility of setting up a "template" of JIRA issues corresponding
to
the newly documented Fluid project process. Here's what I found:
1. Cloned JIRA issues can now also clone subtasks. The newer
version of
JIRA includes this functionality. Now when cloning an issue, there
is a
checkbox for cloning subtasks of the issue. The checkbox is checked
by
default. The cloned issue must have subtasks for this function to do
anything.
Reference: http://jira.atlassian.com/browse/JRA-3742
2. JIRA can be scripted with a scripting language called Jelly. By
writing and running a Jelly script, it appears possible to automate
the
administrative process of creating/cloning the JIRA tasks that map to
the Fluid process for each component.
Reference: http://jira.atlassian.com/browse/JRA-4029
Reference: http://www.atlassian.com/software/jira/docs/latest/jelly.html
Gary
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
Allison Bloodworth
Senior User Interaction Designer
Educational Technology Services
University of California, Berkeley
(415) 377-8243
[EMAIL PROTECTED]
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
