You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Michael Vorburger <mi...@vorburger.ch> on 2020/05/23 13:33:17 UTC
JIRA Dashboard, Blocker issues (and removal of bad 1.4.0 tag)
Hello everyone,
I have created us a fancy new Dashboard on JIRA
<https://jira.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335824#>
for better visibility into our project; details about it are recorded in
FINERACT-1000 <https://jira.apache.org/jira/browse/FINERACT-1000>. (I
*LOVED* how, totally coincidentally, that was our 1000th issue - how very
fitting!)
https://github.com/apache/fineract/pull/929 proposes to add a link to this
new Dashboard to the very top of our README, to make it easy to find.
For example, on this new Dashboard, you could click on the currently 8
issues listed as Blockers in the 3rd table (the one showing a total of
currently 467 Unresolved) to contribute something impactful helping to
unblock a future release - or any other in that table. BTW the Dashboard
has 24 'beginner' tagged issues as the first list... don't be shy! ;-)
BTW I've noticed that a few issues had "tags" such as " p1" etc. To me,
this "parallel dimension" is somewhat confusing, and I propose that we
primarily use the Priority field for triage, and consider issue tags more
"informational".
Best,
M.
PS: While I was doing that and looking at Fix Versions, I've also removed
confusing old 1.4.0 branch & tag on our Git repository at
https://github.com/apache/fineract/, see last comment in FINERACT-873
<https://jira.apache.org/jira/browse/FINERACT-873> for background about
that.
Re: JIRA Dashboard, Blocker issues (and removal of bad 1.4.0 tag)
Posted by Awasum Yannick <aw...@apache.org>.
https://infra.apache.org/infra-contact
On Sat, May 23, 2020 at 3:29 PM Saransh Sharma <sa...@muellners.com>
wrote:
> How can I get in touch with infra guys? Do they have some email ?
>
>
>
> On Sat, 23 May 2020, 19:30 Awasum Yannick, <aw...@apache.org> wrote:
>
>> Hi Saransh,
>>
>>
>> On Sat, May 23, 2020 at 2:48 PM Saransh Sharma <sa...@muellners.com>
>> wrote:
>>
>>> Hey thanks M,
>>>
>>> I would like to know how can I integrate jira issues coming from Apache
>>> fineract to an external application.
>>>
>>> In my case I want to see 👀 and fetch and index in my server from a bit
>>> service which could act as actions.
>>>
>>> Is it possible?
>>>
>>>
>> I have no experience on this but I Googled "integrate jira issues to an
>> external application." and got a lot of results. Anything specific to
>> Apache then you may need to talk to the Infra guys.
>>
>> Thanks.
>>>
>>> On Sat, 23 May 2020, 19:04 Michael Vorburger, <mi...@vorburger.ch> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> I have created us a fancy new Dashboard on JIRA
>>>> <https://jira.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335824#>
>>>> for better visibility into our project; details about it are recorded in
>>>> FINERACT-1000 <https://jira.apache.org/jira/browse/FINERACT-1000>. (I
>>>> *LOVED* how, totally coincidentally, that was our 1000th issue - how very
>>>> fitting!)
>>>>
>>>> https://github.com/apache/fineract/pull/929 proposes to add a link to
>>>> this new Dashboard to the very top of our README, to make it easy to find.
>>>>
>>>> For example, on this new Dashboard, you could click on the currently 8
>>>> issues listed as Blockers in the 3rd table (the one showing a total of
>>>> currently 467 Unresolved) to contribute something impactful helping to
>>>> unblock a future release - or any other in that table. BTW the Dashboard
>>>> has 24 'beginner' tagged issues as the first list... don't be shy! ;-)
>>>>
>>>> BTW I've noticed that a few issues had "tags" such as " p1" etc. To me,
>>>> this "parallel dimension" is somewhat confusing, and I propose that we
>>>> primarily use the Priority field for triage, and consider issue tags more
>>>> "informational".
>>>>
>>>> Best,
>>>> M.
>>>>
>>>> PS: While I was doing that and looking at Fix Versions, I've also
>>>> removed confusing old 1.4.0 branch & tag on our Git repository at
>>>> https://github.com/apache/fineract/, see last comment in FINERACT-873
>>>> <https://jira.apache.org/jira/browse/FINERACT-873> for background
>>>> about that.
>>>>
>>>
Re: JIRA Dashboard, Blocker issues (and removal of bad 1.4.0 tag)
Posted by Saransh Sharma <sa...@muellners.com>.
How can I get in touch with infra guys? Do they have some email ?
On Sat, 23 May 2020, 19:30 Awasum Yannick, <aw...@apache.org> wrote:
> Hi Saransh,
>
>
> On Sat, May 23, 2020 at 2:48 PM Saransh Sharma <sa...@muellners.com>
> wrote:
>
>> Hey thanks M,
>>
>> I would like to know how can I integrate jira issues coming from Apache
>> fineract to an external application.
>>
>> In my case I want to see 👀 and fetch and index in my server from a bit
>> service which could act as actions.
>>
>> Is it possible?
>>
>>
> I have no experience on this but I Googled "integrate jira issues to an
> external application." and got a lot of results. Anything specific to
> Apache then you may need to talk to the Infra guys.
>
> Thanks.
>>
>> On Sat, 23 May 2020, 19:04 Michael Vorburger, <mi...@vorburger.ch> wrote:
>>
>>> Hello everyone,
>>>
>>> I have created us a fancy new Dashboard on JIRA
>>> <https://jira.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335824#>
>>> for better visibility into our project; details about it are recorded in
>>> FINERACT-1000 <https://jira.apache.org/jira/browse/FINERACT-1000>. (I
>>> *LOVED* how, totally coincidentally, that was our 1000th issue - how very
>>> fitting!)
>>>
>>> https://github.com/apache/fineract/pull/929 proposes to add a link to
>>> this new Dashboard to the very top of our README, to make it easy to find.
>>>
>>> For example, on this new Dashboard, you could click on the currently 8
>>> issues listed as Blockers in the 3rd table (the one showing a total of
>>> currently 467 Unresolved) to contribute something impactful helping to
>>> unblock a future release - or any other in that table. BTW the Dashboard
>>> has 24 'beginner' tagged issues as the first list... don't be shy! ;-)
>>>
>>> BTW I've noticed that a few issues had "tags" such as " p1" etc. To me,
>>> this "parallel dimension" is somewhat confusing, and I propose that we
>>> primarily use the Priority field for triage, and consider issue tags more
>>> "informational".
>>>
>>> Best,
>>> M.
>>>
>>> PS: While I was doing that and looking at Fix Versions, I've also
>>> removed confusing old 1.4.0 branch & tag on our Git repository at
>>> https://github.com/apache/fineract/, see last comment in FINERACT-873
>>> <https://jira.apache.org/jira/browse/FINERACT-873> for background about
>>> that.
>>>
>>
Re: JIRA Dashboard, Blocker issues (and removal of bad 1.4.0 tag)
Posted by Awasum Yannick <aw...@apache.org>.
Hi Saransh,
On Sat, May 23, 2020 at 2:48 PM Saransh Sharma <sa...@muellners.com>
wrote:
> Hey thanks M,
>
> I would like to know how can I integrate jira issues coming from Apache
> fineract to an external application.
>
> In my case I want to see 👀 and fetch and index in my server from a bit
> service which could act as actions.
>
> Is it possible?
>
>
I have no experience on this but I Googled "integrate jira issues to an
external application." and got a lot of results. Anything specific to
Apache then you may need to talk to the Infra guys.
Thanks.
>
> On Sat, 23 May 2020, 19:04 Michael Vorburger, <mi...@vorburger.ch> wrote:
>
>> Hello everyone,
>>
>> I have created us a fancy new Dashboard on JIRA
>> <https://jira.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335824#>
>> for better visibility into our project; details about it are recorded in
>> FINERACT-1000 <https://jira.apache.org/jira/browse/FINERACT-1000>. (I
>> *LOVED* how, totally coincidentally, that was our 1000th issue - how very
>> fitting!)
>>
>> https://github.com/apache/fineract/pull/929 proposes to add a link to
>> this new Dashboard to the very top of our README, to make it easy to find.
>>
>> For example, on this new Dashboard, you could click on the currently 8
>> issues listed as Blockers in the 3rd table (the one showing a total of
>> currently 467 Unresolved) to contribute something impactful helping to
>> unblock a future release - or any other in that table. BTW the Dashboard
>> has 24 'beginner' tagged issues as the first list... don't be shy! ;-)
>>
>> BTW I've noticed that a few issues had "tags" such as " p1" etc. To me,
>> this "parallel dimension" is somewhat confusing, and I propose that we
>> primarily use the Priority field for triage, and consider issue tags more
>> "informational".
>>
>> Best,
>> M.
>>
>> PS: While I was doing that and looking at Fix Versions, I've also removed
>> confusing old 1.4.0 branch & tag on our Git repository at
>> https://github.com/apache/fineract/, see last comment in FINERACT-873
>> <https://jira.apache.org/jira/browse/FINERACT-873> for background about
>> that.
>>
>
Re: JIRA Dashboard, Blocker issues (and removal of bad 1.4.0 tag)
Posted by Saransh Sharma <sa...@muellners.com>.
Hey thanks M,
I would like to know how can I integrate jira issues coming from Apache
fineract to an external application.
In my case I want to see 👀 and fetch and index in my server from a bit
service which could act as actions.
Is it possible?
Thanks.
On Sat, 23 May 2020, 19:04 Michael Vorburger, <mi...@vorburger.ch> wrote:
> Hello everyone,
>
> I have created us a fancy new Dashboard on JIRA
> <https://jira.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335824#>
> for better visibility into our project; details about it are recorded in
> FINERACT-1000 <https://jira.apache.org/jira/browse/FINERACT-1000>. (I
> *LOVED* how, totally coincidentally, that was our 1000th issue - how very
> fitting!)
>
> https://github.com/apache/fineract/pull/929 proposes to add a link to
> this new Dashboard to the very top of our README, to make it easy to find.
>
> For example, on this new Dashboard, you could click on the currently 8
> issues listed as Blockers in the 3rd table (the one showing a total of
> currently 467 Unresolved) to contribute something impactful helping to
> unblock a future release - or any other in that table. BTW the Dashboard
> has 24 'beginner' tagged issues as the first list... don't be shy! ;-)
>
> BTW I've noticed that a few issues had "tags" such as " p1" etc. To me,
> this "parallel dimension" is somewhat confusing, and I propose that we
> primarily use the Priority field for triage, and consider issue tags more
> "informational".
>
> Best,
> M.
>
> PS: While I was doing that and looking at Fix Versions, I've also removed
> confusing old 1.4.0 branch & tag on our Git repository at
> https://github.com/apache/fineract/, see last comment in FINERACT-873
> <https://jira.apache.org/jira/browse/FINERACT-873> for background about
> that.
>
Re: JIRA Dashboard, Blocker issues (and removal of bad 1.4.0 tag)
Posted by Awasum Yannick <aw...@apache.org>.
Hi All,
On Sat, May 23, 2020 at 2:34 PM Michael Vorburger <mi...@vorburger.ch> wrote:
> Hello everyone,
>
> I have created us a fancy new Dashboard on JIRA
> <https://jira.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335824#>
> for better visibility into our project; details about it are recorded in
> FINERACT-1000 <https://jira.apache.org/jira/browse/FINERACT-1000>. (I
> *LOVED* how, totally coincidentally, that was our 1000th issue - how very
> fitting!)
>
> Wooow.. Just beautiful. Thanks Mike.
> https://github.com/apache/fineract/pull/929 proposes to add a link to
> this new Dashboard to the very top of our README, to make it easy to find.
>
>
Yes. That makes sense. I just merged your PR:
https://github.com/apache/fineract/pull/929 .
Jira ticket https://issues.apache.org/jira/browse/FINERACT-1000 contains
more details on using the dashboard. ( I also just resolved that to fixed)
For example, on this new Dashboard, you could click on the currently 8
> issues listed as Blockers in the 3rd table (the one showing a total of
> currently 467 Unresolved) to contribute something impactful helping to
> unblock a future release - or any other in that table. BTW the Dashboard
> has 24 'beginner' tagged issues as the first list... don't be shy! ;-)
>
> BTW I've noticed that a few issues had "tags" such as " p1" etc. To me,
> this "parallel dimension" is somewhat confusing, and I propose that we
> primarily use the Priority field for triage, and consider issue tags more
> "informational".
>
> Best,
> M.
>
> PS: While I was doing that and looking at Fix Versions, I've also removed
> confusing old 1.4.0 branch & tag on our Git repository at
> https://github.com/apache/fineract/, see last comment in FINERACT-873
> <https://jira.apache.org/jira/browse/FINERACT-873> for background about
> that.
>