Hi, I've some questions...
- Are sprints created based on what? release, month, another thing? - Epics like 0.13.0 RELEASE are removed after the release is done? Why don't we have previews versions available in Epics? In terms of permissions that I have... I realize there are more options available than before, like edit a ticket, epics, etc, but there are limitations like: - I cannot change the status of stories (like these ones https://issues.apache.org/jira/browse/MAHOUT-2024, https://issues.apache.org/jira/browse/MAHOUT-1956 which I would like to close as they were already merged - I'm not able to create new sprints as it's saying I need Manage Sprints permission. Of course, I'll try to solve the two ones which are open before to create a new one, but it's still a limitation a can see in advance Thanks in advance, André On Wed, Feb 28, 2018 at 10:46 PM, André Santi Oliveira <asobra...@gmail.com> wrote: > The access is working well and thanks for the tips. > > My first approach, for some cases, will be to contact people to get more > information before to take actions on the ticket. > Like that, I can see if comments, re-assign or other actions will be > necessary. > > I'll check what I can do in this case of the overlap. Maybe it'll be > necessary to contact other groups but I'm ready to help on that as well. > > In case you don't agree with the actions I'm taking, please feel free to > give feedback as I'm totally open to it. > > > Cheers, > André > > On Wed, Feb 28, 2018 at 2:11 PM, Andrew Palumbo <ap....@outlook.com> > wrote: > >> Andre, >> >> >> I agree with Trevor, this would be great. You've been added to the >> contributor role. A couple of quick notes: >> >> > - Tickets with status "open" and assigned by people (probably the >> default >> > when we create tickets) >> >> >> We don't have a default asignee currently; the default when creating a >> ticket is "unassigned" >> >> > - Sprint from 2016 still open with no content inside >> > - Sprint name not matching with initial/end date >> >> We've been unable to delete some of the sprint boards, since they some >> happen to overlap other projects, due to the way that ASF Jira is >> configured. This is something that we've had to co-ordinate with INFRA for >> ,so you may need to discuss some issues with them. >> >> >> This would be a great help for the project. >> >> >> >> Thanks very much. >> >> >> --andy >> >> >> ________________________________ >> From: Trevor Grant <trevor.d.gr...@gmail.com> >> Sent: Friday, February 23, 2018 3:46:13 PM >> To: Mahout Dev List >> Subject: Re: Organize JIRA Board >> >> Hi Andre, >> >> That sounds great. >> >> We need to talk to INFRA about how to get you permissions. >> >> Will let you know shortly, >> >> tg >> >> >> On Thu, Feb 22, 2018 at 11:59 PM, André Santi Oliveira < >> asobra...@gmail.com> >> wrote: >> >> > Hi, >> > >> > I'm interested in collaborating with Mahout project and I've followed >> the >> > process to build Mahout from the source and so far it looks like >> everything >> > is working well. >> > >> > Then I jumped into your JIRA board and it looks like you need some help >> to >> > organize that part. Simple things I saw which could be organized like: >> > >> > - Tickets with pull requests available but not linked to the ticket >> > - Tickets with status "open" and assigned by people (probably the >> default >> > when we create tickets) >> > - Sprint from 2016 still open with no content inside >> > - Sprint name not matching with initial/end date >> > - and so on... >> > >> > I really like this part of organizing things and I believe I can start >> help >> > on that. But to help you with this I need a specific access to JIRA >> (more >> > than a simple user that can just create tickets and put comments). >> > >> > Let me know what you think and if you need more information to trust me >> on >> > that. >> > >> > >> > Cheers, >> > André >> > https://github.com/ASOBrasil >> > >> > >
