Re: FW: issue tracker permissions
Dear Guillaume,toggle quoted messageShow quoted text
Thanks for your efforts in this direction. As I already stated before, it is really a pain that you are not able to follow stories or comment when not being a member in a Pivotaltracker project. However, github issues aren’t more than a crutch, probably not even a good one.
For example, GH issues cannot be ordered. They are in the order of creation, priorization is not visible. Therefore, if you look e.g. at the BOSH mirror , there are a bunch of “unstarted” and “unscheduled” issues, the first “started” one comes on page 2. For bugs, it gets more confusing. Most people have the github bot activated, which creates a PT story for each GH issue created. This is already confusing, because you have two places where potentially updates to this bug could be located in, and nobody knows where to look. Add in the mirroring, and now you have three places, see an example for the buildpacks . All of this is not your fault, it is a restriction on how GH deals with issues and the fact that we’re distributing information over more than one place.
While I appreciate your efforts and time spent on this: I strongly feel that is an issue that can only be solved by one of two options:
• The Pivotaltracker team implementing the necessary functionality
• Migrating to a different tracker
I’m trying all I can to push for the first option by talking to Dan and Lisa, but other features seem to be more important to the PT team. In November, it has been a year since I asked for this, so my confidence isn’t very high that it is going to happen at all. For me that just means option two is getting more and more realistic every day.
From: Guillaume Berche <bercheg(a)gmail.com>
Date: Saturday, 24 September 2016 at 12:29
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org>
Cc: Chip Childers <cchilders(a)cloudfoundry.org>, "cholick(a)gmail.com" <cholick(a)gmail.com>, Dan Podsedly <dpodsedly(a)pivotal.io>, Lisa Doan <ldoan(a)pivotal.io>, "Voelz, Marco" <marco.voelz(a)sap.com>
Subject: Re: [cf-dev] Re: FW: issue tracker permissions
The mirroring of foundation projects is around 60% complete. See  for more detailed coverage. This should enable community members to watch the most active foundation backlogs. I received no notifications of negative side effects of this mirroring so
far. I'll proceed with mirroring the remaining projects in the next days/weeks.
There are interesting next steps that could be tackled, such as enabling commenting on the backlogs, or searching across all foundation backlog history, see . Let me know if you have interests in discussing these next steps and current challenges faced by
the mirroring process. The upcoming Frankfurt cfsummit unconference on monday might be a good place for this, I'd propose a subject if I receive some interest.
On Mon, Sep 5, 2016 at 10:21 PM, Guillaume Berche
We have prototyped at Orange an automatic mirroring of Pivotal Tracker (PT) stories into github issues. See pivotaltrackermirror at , and the experimental mirror of the buildpack tracker at . I'd like to thanks the buildpacks team for accepting to join
this experiment and providing us with feedback in the past few weeks.
We hope this could bring the following benefits to the CF community:
1. allow use of the
watching notifications <https://help.github.com/articles/about-notifications/#types-of-notifications> github feature to track progress on public pivotal trackers projects: all stories or selected stories of interest.
2. allow use of
github search features <https://help.github.com/articles/searching-github> to search Pivotal Tracker content (e.g. accross multiple mirrored PT projects, or along with other github repositories hosting the associated code)
3. allow use of
github @mentions <https://help.github.com/articles/basic-writing-and-formatting-syntax/#mentioning-users-and-teams> to contact github accounts associated with PT public projects contributors, in the context with a specific mirrored story
4. mirrored content becomes discoverable: search engines index it, making it easier to find mirrored PT content such as a stack trace
This is still experimental work. We would like to hear community feedback about this initiative (how is it useful?), as well as core contributor teams (are there unexpected side-effects that need to be handled beyond what we fixed so far ?) Do you have
suggestions for enhancements: can you comment/vote/improve in ?
Our plan is to progressively extend this experiment to more trackers listed in  (in a rate of a few projects per week). Please report issues on  if you observe negative side effects, or reply to this email if you have concerns about this mirroring.
There still a fair amount of work ahead to convert this experiment into a stable tool, and opportunities to provide some new cool features to the community. Contributions are welcome :-)
ps: I also recently noticed a PT slack integration  that would also cover use-case #1 (get notifications for all stories in a tracker). I'm not yet sure what it takes to add it to a given channel.
On Sun, May 29, 2016 at 8:05 PM, John Wong
Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a google group and a thread will be built as comment is added.
This at least allow a read-only mirror.
Just a thought...
On Sunday, May 29, 2016, Voelz, Marco <marco.voelz(a)sap.com> wrote:
Dear Dan, dear Lisa, dear Chip, dear community,
sorry for digging out this old issue again and again. If you are just tuning in, here is the situation
I like Pivotal Tracker as a product
I have to use Tracker for my daily work, as it is currently mandatory for all CFF projects and all of them use it
The restrictions in pivotal tracker make it hard to impossible to do the daily stuff you want to do within a large open-source community.
After initially bringing this up in November last year, here are a few of the problems I addressed with Dan in a hangout session in February:
To follow stories in a project you need to be a member of that project. Therefore, you cannot track progress on stories in other projects.
To comment on stories, the same restrictions as above apply
It has been 3 months since Dan and I talked, I’ve checked back every 4 weeks with him and what I’ve heard so far is ideas. I haven’t seen a prototype, any specifics on the current state,
any planning details. It’s not like I’m demanding this feature should be done by now – I just want to know what is going on.
I have to say I am very unhappy in how this topic is treated. From my point of view, it seems like there is a huge lack of transparency and feedback. Please, let me know what’s going on.
I don’t want to switch to a different tracker, such as e.g. trello, but if the requirements of a large open-source community aren’t heard, then I don’t know what else to do about this.
PS: What about a public tracker backlog in tracker, so people can follow their favorite feature stories and see where they are in the planning and when they’re done?
On 16/01/16 13:09, "Voelz, Marco" <marco.voelz(a)sap.com> wrote:
it has now been more than a month since I sent my feedback concerning this feature to the tracker team – I haven't received any reaction to it.
Is there an option you could weigh in for this from the Foundation perspective? That would be great!
Sorry for being so stubborn about this, but in my opinion this is a crucial feature for a bug tracker/backlog which is used in an open-source product. I know that all the people
working directly at pivotal don't feel the pain, because they can either talk directly to everyone in person or have the necessary rights to comment/follow in the other projects, but for everyone else this is really, really a problem.
On 09/12/15 21:20, "Voelz, Marco" <marco.voelz(a)sap.com> wrote:
Thanks for pointing me to this link. However, we seem to have the same problem here: This seems like a fire-and-forget solution. Where does this item go? How can I send it to
other people and have them +1 it, like it, follow it, favorite it or whatever is necessary to indicate that there is more than 1 person wanting this feature?
Thanks and warm regards
On 09/12/15 20:01, "Amit Gupta" <agupta(a)pivotal.io> wrote:
If you're logged in to Tracker, there's a "Help & Updates" link at the top, and one of the options is Provide Feedback.
On Wed, Dec 9, 2015 at 10:59 AM, Voelz, Marco <marco.voelz(a)sap.com> wrote:
I'd happily submit a feature request to build up some visible demand for this – could you point me to the right channel here?
Thanks and warm regards
On 08/12/15 23:01, "Dieu Cao" <dcao(a)pivotal.io> wrote:
Unfortunately in order to follow a story in tracker, the minimum required level is "member" which allows you to create/comment/delete stories in tracker.
I would suggest submitting a request to the pivotal tracker team to help build up evidence that this is a feature that people want.
On Tue, Dec 8, 2015 at 12:49 PM, Matt Cholick <cholick(a)gmail.com> wrote:
Sorry to resurrect an older thread, but I wanted to chime in that this is a frustration I have too. There are several stories in the various CF teams public backlogs that I'd
like to keep track of.
Is it possible for community members to get enough permissions on our tracker accounts to add ourselves to the follow list?
On Mon, Nov 23, 2015 at 3:10 AM, Koper, Dies <diesk(a)fast.au.fujitsu.com> wrote:
Hi Marco, Jan,
I sent an email to Tracker support about that last week because we were hoping to close CLI feature requests on GH and let people follow the stories on Tracker. Support confirmed that people need to have R/W access to a project to do that.
I have just replied to ask if they'd consider an enhancement. Not sure what the proper channel would be to get such a story prioritized.
Will let you know if I get a reply.
Cloud Foundry CLI PM
From: Voelz, Marco [mailto:marco.voelz(a)sap.com]
Sent: Monday, November 23, 2015 8:00 PM
To: Discussions about Cloud Foundry projects and the system overall.
Subject: [cf-dev] Re: FW: issue tracker permissions
Thanks Jan for bringing that up, I've had similar problems with that as well. Any ideas on how to solve this? Is this a feature that the tracker team actively works on?
Hitting cmd+r every few days on the same stories doesn't seem like the best way to stay informed about your favorite features.
On 19/11/15 09:23, "Sievers, Jan" <jan.sievers(a)sap.com> wrote:
>>I was trying to watch a story I am interested in
>>I do have an account but it seems I don't have permissions to watch nor to comment.
>>Is there something I missed?
Sent from Jeff Dean's printf() mobile console