linaro-project-management team mailing list archive

[Jakub Pavelek <jakub.pavelek@xxxxxxxxxx>]

Hi,

I think it is good feature to be able set expected delivery of a feature
with accuracy of one month. This does not change much for people who want
to talk in iterations or quarters anyway.

No-one is proposing to use month-sized cards for roadmapping purposes or
for reviews @TSC/OPSCOM if I read this correctly, that size would fit
subtasks, good again.

Today someone went to play - messed up a structure and introduced bogus
dependencies to my card. It is too easy to do. I did not get email
notifications. Perhaps toothing problems ...

Br,

--jakub



On 19 November 2012 19:19, Ilias Biris <ilias.biris@xxxxxxxxxx> wrote:

>  Hi folks
>
> If you are handling issues in JIRA please keep reading.
>
> With the creation of LEG some changes are coming in JIRA.  Even though the
> tone in this message is like "done deal" I can take your feedback and work
> with you if any change is disruptive - I just had to enable these changes
> to enable LEG to move forward.
>
> --
> 1. fixVersions are going monthly: instead of having only iterations which
> span the periods between Connect events, the fixVersions in JIRA will now
> also reflect monthly periods. The format will be YYYY.MM and I will start
> putting the changes in now.
>
> The existing iteration milestones will still be there at least till next
> Connect - we will reevaluate then. The monthly milestones will be added
> today and will be available for use immediately. Also the monthly
> milestones will be used for eg OPSCOM and TSC card discussions, as well as
> for evaluation of what was done when we go at Connect in March.
>
> --
> 2. Sub-tasks are now enabled for cards. In their field details subtasks
> are similar to normal cards however there are some differences:
>
> - subtasks cannot exist without a parent card. Actually you can only
> create them from viewing a card - menu "more actions" > "create a sub-task"
> - 2 cards cannot have the same sub-task, unless via linking (using the
> "link issue" functionality - see 3 below)
> - subtasks have their own workflow: they do not follow the approval route
> that roadmap cards follow, but they use instead the default jira workflow
> of simple bug resolution: start - in progress - resolved - closed.
> Resolution can be one of: fixed, delivered, won't fix, duplicate,
> incomplete and deferred.
>
> Subtasks are meant for LEG to use instead of blueprints. It will allow the
> breakdown of epic cards into smaller roadmap cards (which could be marked
> against a monthly milestone as indicated in 1) and those can be decomposed
> further to subtasks which can contain a number of work items. The work
> items and other meta headers used in blueprints will be used in the same
> way - with one exception: no need for roadmap id any longer.
>
> --
> 3. Only for LEG: LEG subtasks (that is subtasks in cards for the LEG Jira
> component) are automatically linked to their parent cards. The link type is
> one I created called "Implements": a card is "implemented by" subtasks and
> a subtask "implements" the parent card (or at least part of it). The link
> type is also available to other cards - not just the ones for LEG - you can
> now link cards to other cards using this link type along other default link
> types (blocks, clones, relates to). But the automatic linking only works
> for LEG at the moment.
>
> --
> 4. I have installed a plugin to handle searches for links to other issues
> - this is for convenience only. For those who want to know more this plugin
> is called Craftforge JQL Functions Plugin (v1.3.1) - it is a free plugin
> which allows creating subqueries in JQL using saved filters. More details
> are in
> https://marketplace.atlassian.com/plugins/org.craftforge.jira.craftforge-jql-functions-plugin/version/20120623
>
> Please feel free to share your comments and ask questions. In particular
> note that the use of JIRA for blueprints as well as cards is an experiment
> with LEG.
>
> Best regards,
>
> --
> Ilias Biris ilias.biris@xxxxxxxxxx
> Project Manager, Linaro
> M: +358504839608, IRC: ibiris Skype: ilias_biris
> Linaro.org│ Open source software for ARM SoCs
>
>
>