Puppet Labs issue tracker migration 16 Dec 2013

[Eric Sorenson]

Hi, as I mailed about a little while ago[1], we're migrating issue
tracking for Puppet Labs projects from Redmine to JIRA.

After working through the tooling and integration concerns, we're going
to make the switch on 16th of December.

More info on how this will work:

* Everybody needs to create a new account on JIRA, since we can�t
migrate passwords from redmine to jira.
* If you were watching redmine bugs to track their progress, you will be
notified via email with the new location of the bug in JIRA. You'll need
to set yourself up to watch the bug in JIRA with your newly-created
account.
* Some older issues that we think are obsolete will not be migrated, but
if we made a mistake and forgot to include your favorite bug, there will
be a link on each Redmine issue where you can migrate it with a single
click.
* The Redmine instance will remain up and read-only, because there's a
ton of back history, outgoing links, google indexing, etc that is quite
valuable to keep.
* Projects that use github issues will also migrate, but pull request
workflow remains as-is.

Please let me know if you have any additional questions.

[1] https://groups.google.com/d/topic/puppet-users/4lV1cT6Li-M/discussion

--
Eric Sorenson - eric.s...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

[John Warburton]

* Everybody needs to create a new account on JIRA, since we can’t migrate passwords from redmine to jira.

Is the JIRA link available? From the front page, Bug Tracker points at RedMine . Or do I need to hold my horses?

Thanks

John

[Charlie Sharpsteen]

Hi John,

Updated documentation will be rolled out alongside public access to JIRA on the 16th. Account creation will be opened on that day as well.

Let us know if you have any other questions about the migration!

--

Charlie Sharpsteen

Open Source Support Engineer

Puppet Labs

[R.I. Pienaar]

On Tuesday, December 10, 2013 6:51:51 PM UTC, Eric Sorenson wrote:

Hi, as I mailed about a little while ago[1], we're migrating issue
tracking for Puppet Labs projects from Redmine to JIRA.

After working through the tooling and integration concerns, we're going
to make the switch on 16th of December.

More info on how this will work:

* Everybody needs to create a new account on JIRA, since we can�t
migrate passwords from redmine to jira.
* If you were watching redmine bugs to track their progress, you will be
notified via email with the new location of the bug in JIRA. You'll need
to set yourself up to watch the bug in JIRA with your newly-created
account.
* Some older issues that we think are obsolete will not be migrated, but
if we made a mistake and forgot to include your favorite bug, there will
be a link on each Redmine issue where you can migrate it with a single
click.
* The Redmine instance will remain up and read-only, because there's a
ton of back history, outgoing links, google indexing, etc that is quite
valuable to keep.
* Projects that use github issues will also migrate, but pull request
workflow remains as-is.

Please let me know if you have any additional questions.

I am probably just missing the obvious - in redmine it was possible to subscribe to an entire project and get all activity.  How do I do the same with Jira? 

[Charlie Sharpsteen]

On Monday, December 16, 2013 1:46:45 AM UTC-8, R.I. Pienaar wrote:

I am probably just missing the obvious - in redmine it was possible to subscribe to an entire project and get all activity.  How do I do the same with Jira?

 In JIRA, you can subscribe to any saved issue query and have the updates mailed out on a set schedule. More information can be found here:

  https://confluence.atlassian.com/display/JIRA061/Receiving+Search+Results+via+Email

Updates for all platform projects are also being sent by JIRA to the puppet-bugs mailing list.

[Erik Dalén]

What is the desired workflow for submitting a pull request for a ticket?

The old field for branch seems gone and the issue status "In topic branch awaiting review" is gone as well.

The workflow menu shows 25 different issue statuses and I have no clue which one to choose.

On 10 December 2013 19:51, Eric Sorenson <eric.s...@puppetlabs.com> wrote:

Hi, as I mailed about a little while ago[1], we're migrating issue tracking for Puppet Labs projects from Redmine to JIRA.

After working through the tooling and integration concerns, we're going to make the switch on 16th of December.

More info on how this will work:

* Everybody needs to create a new account on JIRA, since we can’t migrate passwords from redmine to jira.

* If you were watching redmine bugs to track their progress, you will be notified via email with the new location of the bug in JIRA. You'll need to set yourself up to watch the bug in JIRA with your newly-created account.
* Some older issues that we think are obsolete will not be migrated, but if we made a mistake and forgot to include your favorite bug, there will be a link on each Redmine issue where you can migrate it with a single click.
* The Redmine instance will remain up and read-only, because there's a ton of back history, outgoing links, google indexing, etc that is quite valuable to keep.
* Projects that use github issues will also migrate, but pull request workflow remains as-is.

Please let me know if you have any additional questions.

[1] https://groups.google.com/d/topic/puppet-users/4lV1cT6Li-M/discussion

--
Eric Sorenson - eric.s...@puppetlabs.com - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52A762C7.8080709%40puppetlabs.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Erik Dalén

[Jason Antman]

I've gone through and migrated most of the issues I was watching (and
still care about) that weren't already.

I ran into 4 issues that show up with a message of:

"This issue is currently not available for export. If you are
experiencing the issue described below, please file a new ticket in
JIRA. Once a new ticket has been created, please add a link to it that
points back to this Redmine ticket."

Should I do so, or is there a better way of handling this?

The issues in question are 4240, 13602, 17439 and 22902.

Thanks,
j antman

[Charlie Sharpsteen]

On Monday, December 16, 2013 11:37:26 AM UTC-8, Jason Antman wrote:

I've gone through and migrated most of the issues I was watching (and
still care about) that weren't already.

I ran into 4 issues that show up with a message of:

"This issue is currently not available for export. If you are
experiencing the issue described below, please file a new ticket in
JIRA. Once a new ticket has been created, please add a link to it that
points back to this Redmine ticket."

Should I do so, or is there a better way of handling this?

The issues in question are 4240, 13602, 17439 and 22902.

Thanks,
j antman

Hi Jason,

Thanks for bringing these to our attention! Redmine to JIRA issue export has been enabled for:

  -  Puppet Community Package Repository

  -  Puppet Labs Modules

I have migrated 13602, 17439 and 22902. Ticket 4240 is in a project that has not seen significant activity for quite a while and so automatic issue migration will not be set up. For cases like this, we can discuss the status of the ticket on IRC in #puppet-dev.

Let us know if you have any more questions!

[Josh Cooper]

On Mon, Dec 16, 2013 at 8:19 AM, Erik Dalén <erik.gus...@gmail.com> wrote:

What is the desired workflow for submitting a pull request for a ticket?

Charlie wrapped up the documentation for this here: http://docs.puppetlabs.com/community/puppet_projects_workflow.html If you find issues or have questions, please let us know.

 

The old field for branch seems gone and the issue status "In topic branch awaiting review" is gone as well.

Please add a issue link to the PR and set the status to "ready for merge".

To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAAAzDLcqJ800m%2BxvUsBnQgujVM22YU8zyiPGubadNz9FNpcs_Q%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--

Josh Cooper

Developer, Puppet Labs