Return-Path: X-Original-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-allura-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CAED4106AB for ; Wed, 24 Jul 2013 14:43:31 +0000 (UTC) Received: (qmail 90541 invoked by uid 500); 24 Jul 2013 14:43:31 -0000 Delivered-To: apmail-incubator-allura-dev-archive@incubator.apache.org Received: (qmail 90460 invoked by uid 500); 24 Jul 2013 14:43:27 -0000 Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: allura-dev@incubator.apache.org Delivered-To: mailing list allura-dev@incubator.apache.org Received: (qmail 90432 invoked by uid 99); 24 Jul 2013 14:43:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2013 14:43:25 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of noreply@sourceforge.net designates 216.34.181.60 as permitted sender) Received: from [216.34.181.60] (HELO smtp.ch3.sourceforge.com) (216.34.181.60) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2013 14:43:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.com; s=x; h=Date:Message-ID:Subject:Reply-To:From:To:MIME-Version:Content-Type; bh=JO+EDJ7jc8229SBn1A132e8/fET4VhzYf7MX5HInru0=; b=omsWpha52PHM4I1yyAzr/3Du3UExQnKffItAZvONc3famXt5q/CShdQsRELiv56wVmD2rI7y0ICcCFpqyf1VTNfMFbgfQaHzMJLTT5AQ+pP/Pq4YdKKyC7mYuTGc1c+2MdY0mPVq2Esr2QESjnuToUvTNu13yQoqsfVEEvch0jI=; Received: from localhost ([127.0.0.1] helo=sfs-alluradaemon-3.v29.ch3.sourceforge.com) by sfs-alluradaemon-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V20HD-0005jn-U3 for allura-dev@incubator.apache.org; Wed, 24 Jul 2013 14:42:51 +0000 Content-Type: multipart/related; boundary="===============7605891762710347125==" MIME-Version: 1.0 To: "[allura:tickets] " <6477@tickets.allura.p.re.sf.net> From: "Cory Johns" Reply-To: "[allura:tickets] " <6477@tickets.allura.p.re.sf.net> Subject: [allura:tickets] #6477 Support private tickets in Google Code Issues importer Message-ID:

Date: Wed, 24 Jul 2013 14:42:51 +0000 X-Virus-Checked: Checked by ClamAV on apache.org --===============7605891762710347125== Content-Type: multipart/alternative; boundary="===============8854392914070341956==" MIME-Version: 1.0 --===============8854392914070341956== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Somehow, I missed the [Permissions system documentation](https://code.google.com/p/support/wiki/Permissions), in favor of which the "`private`" label has been depreciated. Private tickets are indicated by some form of a "`Restrict-View-*`" label, which restrict the ability to view the ticket to users with that permission, which is managed on the People tab. It's a bit more fine-grained than Allura's private tickets, though it can be replicated via the use of groups. It's unclear how common the usage of this is, but it's certainly more prevalent than the "`private`" label. --- ** [tickets:#6477] Support private tickets in Google Code Issues importer** **Status:** open **Labels:** import google-code **Created:** Mon Jul 22, 2013 05:46 PM UTC by Cory Johns **Last Updated:** Mon Jul 22, 2013 05:46 PM UTC **Owner:** nobody Apparently, GC does in fact support private tickets via the label "private." (NB: when adding the "private" label, GC notes that you're using "an uncommon label" but it does make the ticket only visible by project members.) To support importing them, we will need to perform authentication via [AuthSub](https://developers.google.com/accounts/docs/AuthForWebApps), requiring additional info from the user during either tool or project import. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. --===============8854392914070341956== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

Somehow, I missed the Permissions system documentation, in favor of which the "private" label has been depreciated.

Private tickets are indicated by some form of a "Restrict-View-*" label, which restrict the ability to view the ticket to users with that permission, which is managed on the People tab.

It's a bit more fine-grained than Allura's private tickets, though it can be replicated via the use of groups.

It's unclear how common the usage of this is, but it's certainly more prevalent than the "private" label.


[tickets:#6477] Support private tickets in Google Code Issues importer

Status: open
Labels: import google-code
Created: Mon Jul 22, 2013 05:46 PM UTC by Cory Johns
Last Updated: Mon Jul 22, 2013 05:46 PM UTC
Owner: nobody

Apparently, GC does in fact support private tickets via the label "private." (NB: when adding the "private" label, GC notes that you're using "an uncommon label" but it does make the ticket only visible by project members.)

To support importing them, we will need to perform authentication via AuthSub, requiring additional info from the user during either tool or project import.


Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

--===============8854392914070341956==-- --===============7605891762710347125==--