Talk:JIRA Migration

MPDL

Username changes
n.bulatovic@mpdl.mpg.de natasab (done)

u.tschida@mpdl.mpg.de uat (done)

kleinfercher kleinfe (done)

buechner@mpdl.mpg.de kab (done)

forkel@mpdl.mpg.de robert (done)

saquet@mpdl.mpg.de bastien (done)

franke@mpdl.mpg.de fram (done)

malte.dreyer@mpdl.mpg.de mad (done, username was m.dreyer@mpdl.mpg.de)

v.makarenko@mpdl.mpg.de vdm (done)

kanellopoulou@mpdl.mpg.de denya(done)

boosen@mpdl.mpg.de mbo(done)

jmueller@mpdl.mpg.de juliane(done)

kurt@mpdl.mpg.de julia(done - username was only "kurt")

unfried@mpdl.mpg.de dns (done)

schraut@mpdl.mpg.de schraut (done - username was "t.schraut" only)

frank www (done)

haarlaender msh (done)

kiefl kie (done, username was "kiefl@mpdl.mpg.de")

gros@mpdl.mpg.de andi (changed by NBU) n.kondic@mpdl.mpg.de nek (changed by NBU)


 * It would be nice if the username all have the same 'style'. Currently we have
 * nicknames
 * given name, family name
 * family name, given name
 * This makes it hard to find people in the 'assign to' list, because it is not ordered properly --Friederike 10:24, 12 February 2010 (UTC)

"Product Backlogs"
--Ulla 17:02, 10 February 2010 (UTC) One benefit of having JIRA (partly) public would be to provide the overall backlogs/"roadmaps" to the public. (Currently, PubMan backlog is spread over the aquarium, FACES is an xls.file, VIRR is in Colab etc.) To be able to provide good insight, we would need to have information on I assume we would have to define different kind of workflow/task for this "project" as for the projects mentioned on main page.
 * priority (use current Priority values?)
 * stakeholder (use current components?)
 * Functional domain of the requirement (use summary?)
 * Requirement (use summary?)
 * Candidate for version xy (hmmm..optional)
 * hmm... we have agreed to bring all in one single pubman backlog project, to avoid multiple projects per solution.. not certain as well if the stakeholders would be of interest for the public. Now, we need to actually see how/where to keep this info. --Natasa 09:55, 11 February 2010 (UTC)

Privacy issues
--Ulla 17:41, 11 February 2010 (UTC) Feedback SvM Meeting: The last status of discussion in autumn 2009 was to postpone decision of what exaclty can be made public under which circumstances. Not sure on current state of discussion/decisions, in any case, for SvM still valid requirement:
 * aliases
 * remove tracks of "real life persons" in any comment/summary/ visible to public.

Other projects
--Ulla 17:44, 11 February 2010 (UTC): Is it right that all the other projects in JIRA not mentioned on main page (e.g. PubMan Migration, Digital Collection, Cluster Jus etc.)will be migrated 1:1 (i.e. not public) to the new JIRA version?

Custom fields

 * TODO: upload images for bird-eye projects (done)