Ok. Sent from Gmail Mobile
On Wed, Mar 19, 2025 at 12:59 PM Felix van Hove <fvanh...@gmx.de.invalid> wrote: > They are not UI bugs at all. > > > https://issues.apache.org/jira/browse/FINERACT-2218?jql=project%20%3D%20FINERACT%20AND%20reporter%20in%20(fvanhove)%20ORDER%20BY%20created%20DESC > > I just notice that something in the UI doesn't work, because Fineract > doesn't work. E.g. currently we can't provide the "Create Survey" > functionality in the UI, because Fineract (when asked to create a > survey) seems to have a problem even with the expected date format. > > On 19/03/2025 15:04, James Dailey wrote: > > Felix - side thread: Mifos UI bugs also don’t belong on Fineract ; > unless > > you mean UI bugs are traced to a Fineract processing API. In which case > I > > wouldn’t call them UI bugs. > > > > > > > > > > > > > > On Wed, Mar 19, 2025 at 2:56 AM Ádám Sághy <adamsa...@gmail.com> wrote: > > > >> Hi > >> > >> Let me chime in: > >> > >> i think we should not discourage people from raising bug tickets. those > >> are important. > >> > >> i agree with clean slate principal but maybe i would increase from 3 > >> months to 6 months the threshold. > >> > >> Also it would be the best wehn a bug ticket is raised then the DEV mail > >> list should be informed. > >> > >> Whether it is before or after i am not sure. > >> > >> i think we just dont have visibility on the newly created bugs and those > >> are not reviewed and discussed, so noone's picking it up. > >> > >> What do you think? > >> > >> Regards > >> Adam > >> > >> Sent from my iPhone > >> > >>> On 19 Mar 2025, at 10:45, Felix van Hove <fvanh...@gmx.de.invalid> > >> wrote: > >>> > >>> First of all, let me join others in thanking Adam! > >>> > >>> However... > >>> > >>>> do not simply create a ticket and expect it to be fixed. Please close > >>>> your tickets if you aren't going to work on it, or if you find no one > >>>> willing to work on it. > >>> > >>> In working on the UI and following Slack one comes across Fineract bugs > >>> frequently. (I created 3.) I assumed the Fineract project profited from > >>> being made aware of them, even if I don't intend to fix any of them, > >>> neither want to find someone (via Slack? by emailing active > developers?) > >>> to fix them. > >>> > >>> So does this mean someone like me should stop pointing out bugs? Or > feel > >>> obliged to return after x weeks to close them, because no one seems to > >>> have picked them up? > >>> > >>> Felix > >>> > >>>> On 19/03/2025 04:27, James Dailey wrote: > >>>> Else-thread I complemented Adam for his great work on over 100 tickets > >>>> recently. Just going through and removing some cruft is important. > >>>> > >>>> But, we have a LOT more to do. Also, since we have a number of new > >> people > >>>> here, I'd like to emphasize something: Please do not simply create a > >>>> ticket and expect it to be fixed. Please close your tickets if you > >> aren't > >>>> going to work on it, or if you find no one willing to work on it. If > >> what > >>>> you have are ideas, then please bring them to the listserv and find > >> common > >>>> ground with others. > >>>> > >>>> Leaving tickets open for hundreds of days doesn't help the project in > my > >>>> view. Below I'm pulling a few reports from the JIRA project. > >>>> > >>>> The average time to fix an issue since Oct 30, 2020 is over 450 days > on > >>>> this project. MOST of this is because a LOT of "abandoned" items stay > >> open > >>>> indefinitely. Maybe they got fixed in the meantime with some other > >> effort, > >>>> or maybe they are a good idea, but leaving them open isn't useful to > us. > >>>> Please recall that tickets are closed but not lost. > >>>> > >>>> I would propose that we close any ticket over 3 months old that is not > >>>> currently receiving any attention, with "will not fix" and give our > >> project > >>>> a "fresh start". Maybe we need to use a status like "abandoned" to > >> help > >>>> find them again. > >>>> > >>>> From my jira queries, there are 311 tickets older than two years ( > i.e. > >>>> created over two years ago and still marked open). > >>>> > >>>> There are 41 tickets created within the last three months which remain > >>>> open. This seems about right. So, I am proposing that we close all > >> but > >>>> about 41 tickets. > >>>> > >>>> We did this a few years ago and closed several hundred in Q4 2022. > >>>> > >>>> thoughts... > >>>> > >>>> Please see the stats below. > >>>> Data Table > >>>> PeriodIssues ResolvedTotal Resolution TimeAvg. Resolution Time > >>>> Q4/2020 19 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2020-10-01+AND+resolutiondate+%3C%3D+%222020-12-31+23%3A59%22 > >>> > >>>> 3350 176 > >>>> Q1/2021 33 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2021-01-01+AND+resolutiondate+%3C%3D+%222021-03-31+23%3A59%22 > >>> > >>>> 4591 139 > >>>> Q2/2021 20 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2021-04-01+AND+resolutiondate+%3C%3D+%222021-06-30+23%3A59%22 > >>> > >>>> 3410 170 > >>>> Q3/2021 21 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2021-07-01+AND+resolutiondate+%3C%3D+%222021-09-30+23%3A59%22 > >>> > >>>> 5582 265 > >>>> Q4/2021 66 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2021-10-01+AND+resolutiondate+%3C%3D+%222021-12-31+23%3A59%22 > >>> > >>>> 12484 189 > >>>> Q1/2022 64 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2022-01-01+AND+resolutiondate+%3C%3D+%222022-03-31+23%3A59%22 > >>> > >>>> 5409 84 > >>>> Q2/2022 46 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2022-04-01+AND+resolutiondate+%3C%3D+%222022-06-30+23%3A59%22 > >>> > >>>> 5989 130 > >>>> Q3/2022 78 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2022-07-01+AND+resolutiondate+%3C%3D+%222022-09-30+23%3A59%22 > >>> > >>>> 4367 55 > >>>> Q4/2022 339 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2022-10-01+AND+resolutiondate+%3C%3D+%222022-12-31+23%3A59%22 > >>> > >>>> 536929 1583 > >>>> Q1/2023 20 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2023-01-01+AND+resolutiondate+%3C%3D+%222023-03-31+23%3A59%22 > >>> > >>>> 356 17 > >>>> Q2/2023 4 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2023-04-01+AND+resolutiondate+%3C%3D+%222023-06-30+23%3A59%22 > >>> > >>>> 256 64 > >>>> Q3/2023 71 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2023-07-01+AND+resolutiondate+%3C%3D+%222023-09-30+23%3A59%22 > >>> > >>>> 15402 216 > >>>> Q4/2023 41 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2023-10-01+AND+resolutiondate+%3C%3D+%222023-12-31+23%3A59%22 > >>> > >>>> 11643 283 > >>>> Q1/2024 17 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2024-01-01+AND+resolutiondate+%3C%3D+%222024-03-31+23%3A59%22 > >>> > >>>> 3252 191 > >>>> Q2/2024 7 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2024-04-01+AND+resolutiondate+%3C%3D+%222024-06-30+23%3A59%22 > >>> > >>>> 1044 149 > >>>> Q3/2024 1 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2024-07-01+AND+resolutiondate+%3C%3D+%222024-09-30+23%3A59%22 > >>> > >>>> 5 5 > >>>> Q4/2024 7 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2024-10-01+AND+resolutiondate+%3C%3D+%222024-12-31+23%3A59%22 > >>> > >>>> 2457 351 > >>>> Q1/2025 116 > >>>> < > >> > https://issues.apache.org/jira/issues/?jql=project+%3D+FINERACT+AND+resolutiondate+%3E%3D+2025-01-01+AND+resolutiondate+%3C%3D+%222025-03-31+23%3A59%22 > >>> > >>>> 106650 919 > >>>> > >>>> > >>>> > >>>> > >>>> From our JIRA - Created vs Resolved. > >>>> > >>>> PeriodCreatedResolved > >>>> Q4/2020 37 19 > >>>> Q1/2021 55 33 > >>>> Q2/2021 22 20 > >>>> Q3/2021 37 21 > >>>> Q4/2021 66 66 > >>>> Q1/2022 97 64 > >>>> Q2/2022 92 46 > >>>> Q3/2022 101 78 > >>>> Q4/2022 90 339 > >>>> Q1/2023 68 20 > >>>> Q2/2023 32 4 > >>>> Q3/2023 42 71 > >>>> Q4/2023 46 41 > >>>> Q1/2024 37 17 > >>>> Q2/2024 31 7 > >>>> Q3/2024 21 1 > >>>> Q4/2024 28 7 > >>>> Q1/2025 57 116 > >>>> > >>> > >> > > > >
