Can we give any authenticated apache jira user contributor status? On Tue, Jul 9, 2019, 08:05 Michael Vorburger <[email protected]> wrote:
> On Mon, Jul 8, 2019 at 11:02 PM Mohit Sinha <[email protected]> > wrote: > >> I can't see the 'Assign to me' link. It's uneditable. >> > > Mohit, could you retry now? (If it doesn't work immediately, you may have > to logout and login back to the Apache JIRA.) > > I've just added you as a Contributor (not Committer) via "Add user to a > role" on > https://issues.apache.org/jira/plugins/servlet/project-config/FINERACT/roles > (available to some of us who have JIRA administration roles). The details > are explained on > https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization > . > > I've noticed that we have only 7 contributors listed in the JIRA > Administration. As far as I am concerned, we should grant the Contributor > (not Committer) role much more liberally - I see very little "risk" in > letting more people Edit or Assign or Link Issues. I'm happy to add > anyone else who replies to this with "me too please" as a Contributor. > > > >> On Tue, Jul 9, 2019 at 12:42 AM Awasum Yannick <[email protected]> wrote: >> >>> Hi Mohit, >>> >>> Fineract uses Git branches to host versions on github: >>> Fineract 1.2 has been released: >>> https://github.com/apache/fineract/tree/1.2.0 >>> Fineract 1.3 and 1.3.1 planned for upcoming release: >>> https://github.com/apache/fineract/tree/1.3.1 >>> >>> Next version of Fineract 1.x will be 1.4 , this is what you need to use >>> for new issues. >>> >>> Also add more details/description to ur issues. >>> >>> I also see the link "Assign to me", Click on that and the issue should >>> be assigned to you: >>> [image: image.png] >>> >>> >>> On Mon, Jul 8, 2019 at 6:00 PM Mohit Sinha <[email protected]> >>> wrote: >>> >>>> Hey, >>>> I am not a committer in Apache Fineract, just an individual contributor. >>>> I have created some JIRA issues because they were big changes and >>>> needed to be properly documented. >>>> I noticed that I couldn't assign them to myself. >>>> >>>> https://jira.apache.org/jira/browse/FINERACT-767 >>>> https://jira.apache.org/jira/browse/FINERACT-759 >>>> >>>> I haven't resolved them, because it asks for some fields like affect >>>> versions etc, about which I have no idea. >>>> >>>> Regards >>>> Mohit >>>> >>>> On Mon, Jul 8, 2019 at 10:35 PM Santosh Math < >>>> [email protected]> wrote: >>>> >>>>> Hi Robert, >>>>> Thank you. >>>>> >>>>> On Mon, Jul 8, 2019 at 7:58 PM Ippez Robert <[email protected]> >>>>> wrote: >>>>> >>>>>> I would like to join on the team of QA. Please consider me as part of >>>>>> the team >>>>>> >>>>>> Thanks >>>>>> Regards >>>>>> Ippez Robert >>>>>> >>>>>> On Mon, Jul 8, 2019 at 3:58 PM Santosh Math < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Myrle, >>>>>>> Sure. I will help others to do QA. >>>>>>> >>>>>>> On Mon, Jul 8, 2019 at 6:18 PM Myrle Krantz <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hey Santosh, >>>>>>>> >>>>>>>> We can adjust the workflow in Jira to reflect the need for QA. >>>>>>>> It's not necessary to assign to one specific person for QA, and it >>>>>>>> might >>>>>>>> discourage others from joining in on that very important task. A truck >>>>>>>> factor of 1 is a bad thing for any project. >>>>>>>> >>>>>>>> Santosh, would you be willing to help others learn to do QA as >>>>>>>> well? Would the rest of y'all like me to edit our Jira workflow to >>>>>>>> make >>>>>>>> the QA step an explicit part of it? >>>>>>>> >>>>>>>> Best, >>>>>>>> Myrle >>>>>>>> >>>>>>>> On Mon, Jul 8, 2019 at 2:20 PM Santosh Math < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi Awasum, >>>>>>>>> Whenever ticket is raised , it's assigned to developer/coder first >>>>>>>>> so that he can get notification to work on it. Once it's 'Resolved' , >>>>>>>>> then >>>>>>>>> the same ticket is assigned QA so that QA person get notification >>>>>>>>> that he >>>>>>>>> can start QA on that. After QA , if the ticket is not properly >>>>>>>>> resolved , >>>>>>>>> then QA person will assign it back to developer with comments. If it >>>>>>>>> is >>>>>>>>> resolved, the QA person will close the ticket. >>>>>>>>> Assigning a ticket is part of the workflow . There is nothing to >>>>>>>>> do with taking credit or not. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Jul 8, 2019 at 3:54 PM Awasum Yannick <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi Santosh, >>>>>>>>>> >>>>>>>>>> Assigning an issue to you which has been fixed by another person >>>>>>>>>> is not a good idea. People want to take credit for their work. From >>>>>>>>>> this >>>>>>>>>> information we can know who to invite as committer and it be part of >>>>>>>>>> their >>>>>>>>>> CV(just record). >>>>>>>>>> >>>>>>>>>> Anyways, We do it via Github PRs. Should be a simpler way to >>>>>>>>>> search and assign the right person who completed a task. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Jul 8, 2019 at 5:04 AM Santosh Math < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Awasum, >>>>>>>>>>> If the issues are fixed/resolved , those tickets should be >>>>>>>>>>> assigned to me. You can simply use filter . Go to Issues > Search >>>>>>>>>>> for >>>>>>>>>>> Issues . In next page , Select project as 'Apache Fineract' and >>>>>>>>>>> select >>>>>>>>>>> status , tick only 'Resolved'. It would list all the tickets which >>>>>>>>>>> are in >>>>>>>>>>> resolved status. >>>>>>>>>>> >>>>>>>>>>> On Mon, Jul 8, 2019 at 3:07 AM Awasum Yannick <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi All, >>>>>>>>>>>> >>>>>>>>>>>> I wonder if we could make the process of assigning an issue to >>>>>>>>>>>> someone other than yourself on Fineract JIRA? >>>>>>>>>>>> >>>>>>>>>>>> There are cases where issues have been fixed in the past and we >>>>>>>>>>>> need to assign that to the right person when closing these >>>>>>>>>>>> issues... >>>>>>>>>>>> >>>>>>>>>>>> Does anyone have an idea on what to do to make it easy to >>>>>>>>>>>> search and assign anyone on Issues? >>>>>>>>>>>> >>>>>>>>>>>> I noticed this a few times.. >>>>>>>>>>>> >>>>>>>>>>>> Thanks >>>>>>>>>>>> Awasum >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Thanks & Regards >>>>>>>>>>> >>>>>>>>>>> Santosh Math >>>>>>>>>>> >>>>>>>>>>> *QA Engineer* >>>>>>>>>>> >>>>>>>>>>> *Conflux Technologies Pvt Ltd >>>>>>>>>>> <http://www.confluxtechnologies.com/>* >>>>>>>>>>> | *Office*: +91-080-41208662 | >>>>>>>>>>> >>>>>>>>>>> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st >>>>>>>>>>> Block, Bengaluru, Karnataka, 560043 INDIA >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Thanks & Regards >>>>>>>>> >>>>>>>>> Santosh Math >>>>>>>>> >>>>>>>>> *QA Engineer* >>>>>>>>> >>>>>>>>> *Conflux Technologies Pvt Ltd >>>>>>>>> <http://www.confluxtechnologies.com/>* >>>>>>>>> | *Office*: +91-080-41208662 | >>>>>>>>> >>>>>>>>> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, >>>>>>>>> Bengaluru, Karnataka, 560043 INDIA >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks & Regards >>>>>>> >>>>>>> Santosh Math >>>>>>> >>>>>>> *QA Engineer* >>>>>>> >>>>>>> *Conflux Technologies Pvt Ltd <http://www.confluxtechnologies.com/>* >>>>>>> | *Office*: +91-080-41208662 | >>>>>>> >>>>>>> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, >>>>>>> Bengaluru, Karnataka, 560043 INDIA >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Ippez Roberts >>>>>> Founder/C.E.O - Swift3 Technologies (U) Ltd >>>>>> "Redefining Next Generation I/O Systems" >>>>>> P.O.Box 155, Moyo >>>>>> UGANDA. >>>>>> Tel: +256777421862/775686538 >>>>>> Skype ID: ippez.robert1 >>>>>> Email: [email protected] >>>>>> >>>>> >>>>> >>>>> -- >>>>> Thanks & Regards >>>>> >>>>> Santosh Math >>>>> >>>>> *QA Engineer* >>>>> >>>>> *Conflux Technologies Pvt Ltd <http://www.confluxtechnologies.com/>* >>>>> | *Office*: +91-080-41208662 | >>>>> >>>>> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, >>>>> Bengaluru, Karnataka, 560043 INDIA >>>>> >>>>
