Re: JIRA migrated

From: Aristedes Maniatis (ar..sh.com.au)
Date: Sat Mar 21 2009 - 21:28:25 EDT

  • Next message: Andrus Adamchik: "Re: Issues Opened: week of 2009-03-23"

    On 22/03/2009, at 9:39 AM, Henri Yandell wrote:

    > On Sat, Mar 21, 2009 at 3:11 PM, Aristedes Maniatis <ar..sh.com.au>
    > wrote:
    >>
    >> * can we get back our header logo and styling? I'm happy to do it,
    >> if it can
    >> be customised per project and I can be given appropriate access.
    >
    > Nope (I know, I liked the Cayenne l&f too).

    OK. Maybe Atlassian will implement this one day in Jira. If you agree,
    please vote for the issue I found:

    http://jira.atlassian.com/browse/JRA-11133

    Personally I dislike the way the Apache Foundation is so lax with
    branding. Although the feather is mostly standardised, the text "The
    Apache Software Foundation" is presented in a different font and
    layout everywhere it appears. And at the top of the Jira page along
    the with URL which presumably you know since you are using a web
    browser to get there. Anyhow, a conversation for another list...

    Maybe you could change the purple-red header colour to match one of
    the reds from the feather?

    >> * If we want to customise our workflow or permissions do we ask you
    >> to set
    >> up these? I see that permissions are set to "standard permissions"
    >> but I
    >> don't really know what that means. I assume any user can create
    >> tasks and
    >> comment on tasks, but only committers, etc can change the milestone
    >> or
    >> status?
    >
    > Generally we'd like to not see customization. You'll need to explain
    > why Cayenne is special compared to other projects, but there are fair
    > reasons to want specialness. For permissions, you use the project role
    > concept to manage your project rather than the jira groups.

    OK. I assume it is useful to be able to report across projects to have
    their workflows and statuses match. However we now have a lot of
    rubbish in our issue types:


    We are likely to get people picking inappropriate tasks types. Surely
    "new Jira project" should be restricted to the Infrastructure project
    or something? And we don't want to encourage questions in our Jira
    since we use the mailing list for help. I don't even know what RTC
    means. Ideally, we only have "bugs" and "new features".

    I notice that some of our SVN commits are doubled up, but that might
    have been that way from before the migration:

    https://issues.apache.org/jira/browse/CAY-1167?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-commits-tabpanel

    * Should the repository at the left point to Cayenne?

    * Can the commit revision number point to: http://fisheye6.atlassian.com/changelog/cayenne/?cs=733975
      instead? Fisheye is so much more useful than the bare bones viewcvs.

    Cheers
    Ari

    -------------------------->
    ish
    http://www.ish.com.au
    Level 1, 30 Wilson Street Newtown 2042 Australia
    phone +61 2 9550 5001 fax +61 2 9550 4001
    GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A



    This archive was generated by hypermail 2.0.0 : Sun Mar 22 2009 - 08:53:24 EDT