starred/SuiteCRM-SuiteCRM

Fork 0

mirror of https://github.com/SuiteCRM/SuiteCRM.git synced 2026-03-02 19:16:58 -05:00

Previous Sprint (13) #3812

New issue

Closed

opened 2026-02-20 16:10:11 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-20 16:10:11 -05:00

Owner

Originally created by @samus-aran on GitHub (Jul 1, 2019).

Hi Everyone!

A little late to the party (again) but I’ll mark it in the calendar! As I said previously lets make this a sprint thing which is usually every 2 weeks but as this is new please allow a little of logistic re-jigging to get the right groove.

So, a Sprint 12 review & Sprint 13 planning discussion!

How did we all do?

Lets break this down….

To Do	In Progress	In Review	Done
7	3	7	4

That works out to be 19% Done, 33% in review & in total 66% that was tackled (Done, In Review & In Progress). Thats a great start!

Out of those the core team help tackle 12/14 of these issues, whether it was assisting or taking ownership and there was 4 issues that were addressed/helped by the community.

For the outstanding issues we have 3 assigned to Core and 4 which haven't been touched with the Help Wanted label.

Which leads to the question is would we transfer these issues onto the next sprint or enforce that they be re-nominated as it perhaps wasn't as much as a priority to the community. Now I'm not saying these aren't a higher priority but we need to ensure that within each sprint we tackle items that we feel we can achieve i.e. that a community member feels they can contribute to.

Now what I have identified below is the same list we had for Sprint 12 discussion which was deemed suitable for community to approach. Some have been tackled some haven't... should these be 're-nominated'?

Concept	Actionable Task	Github Issue	Assigned	Complexity	Sprint	Comment
Emails	Test Coverage	#7299	Core/Community	Medium	12, 13
Emails	~~Attachments Should not be Sending on Reply~~	#7071	Community	Low	12	DONE
Emails	Inline Images not shown in received/sent Emails	#6470	Core/Community	Medium	12, 13
Emails	~~Admin can not edit User's Mail Accounts~~	#7249	Community	Medium	12	DONE
Emails	Incoming IMAP mail issues	#7186	Community	Medium	12, 13	Needs help troubleshooting
Themes	Add in Max 3 columns Support	#3310	Core/Community	Medium	13
Themes	Reduce Padding Edit/Detail/List	#7373	Core/Community	Low	13
Misc	Include a Composer section in Documentation	https://github.com/salesagility/SuiteDocs/issues/273	Core/Community	Low	12, 13
Misc	Develop PRs	#3007, #6602, #6672	Community	-	-

Items still allocated to the Core (potentially Community too) team

Concept	Actionable Task	Github Issue	Assigned	Complexity	Sprint	Comment
Emails	~~Delete Emails~~	#3727	Core	-	12	DONE
Emails	See Attachments on Non Imported Emails	#5190	Core	High	12	Moved to 13 as it is a tough one...
Emails	Can’t filter on multiple Inboxs/Folders	#7279	Core	High	12, 13
Emails	~~Group Email Accounts Not Respecting Reply to Admin restriction~~	#6992	Core	Medium	12	IN REVIEW
Emails	Attachments Not being Sent (multiple areas)	#6968, #5520, #5552, #2174	Core/Community	High	12, 13
Emails	Differences between Imported/Non Imported Email Views	#4881	Core	Medium	12, 13
Emails	~~Auto Importing Not Working~~	#6866, #6534	Core	Medium	12	DONE
Emails	Bulk Actions is disabled	#7298	Core	Low	12	In Progress
Themes	Update documentation on customising Themes	#5440, https://github.com/salesagility/SuiteDocs/issues/291	Core	Low	12, 13
Themes	List View: Mirror Subpanels + on smaller screens		Core	Medium	13
Misc	~~Confirm that issue was resolved regarding ElasticSearch issue on shared hosting~~		Core	Medium	12	UNABLE TO TEST
Misc	Update documentation that Shared Hosting should be OK with ElasticSearch		Core	Low	12, 13
Misc	Create a Migration Guide to help others to upgrade	https://github.com/salesagility/SuiteDocs/issues/292	Core/Community	Low	12, 13	Lets make a group discussion for this
Misc	Update documentation to state that GDPR is not mandatory option	https://github.com/salesagility/SuiteDocs/issues/293	Core	Low	12
Misc	~~Popup Studio and Calendar don't auto-close~~	#3756	Core/Community	Low	12, 13	IN REVIEW
Misc	~~housekeep session files~~	#3157	Core	Medium	12, 13	IN REVIEW
Misc	Test Suite Improvements	#7344	Core/Community	Medium	12, 13	ON GOING

We will also be pulling in High Priorities into this sprint as these should always be tackled ASAP.

Retrospect this housekeeping is abit fidgetity.. perhaps it better just to identify the issues people want to nominate and move them into the sprints backlog - the To Do column will be what has been allocated out and people have identified their interest in tackle that said issue?

https://github.com/salesagility/SuiteCRM/projects/7

I feel comfortable that we still have a lot of things to tackle in this sprint but we should be keep this discussion open to improve our processes & gain feedback 👍

Originally created by @samus-aran on GitHub (Jul 1, 2019). Hi Everyone! A little late to the party (again) but I’ll mark it in the calendar! As I said previously lets make this a sprint thing which is usually every 2 weeks but as this is new please allow a little of logistic re-jigging to get the right groove. So, a Sprint 12 review & Sprint 13 planning discussion! How did we all do? Lets break this down…. To Do | In Progress | In Review | Done ------------ | ------------- | ------------- | ------------- 7 | 3 | 7 | 4 ![Screenshot_2019-07-01 salesagility SuiteCRM](https://user-images.githubusercontent.com/4041275/60433399-a5f6f580-9bfc-11e9-8639-00136180981f.png) That works out to be 19% Done, 33% in review & in total 66% that was tackled (Done, In Review & In Progress). Thats a great start! Out of those the core team help tackle 12/14 of these issues, whether it was assisting or taking ownership and there was 4 issues that were addressed/helped by the community. For the outstanding issues we have 3 assigned to Core and 4 which haven't been touched with the Help Wanted label. Which leads to the question is would we transfer these issues onto the next sprint or enforce that they be re-nominated as it perhaps wasn't as much as a priority to the community. Now I'm not saying these aren't a higher priority but we need to ensure that within each sprint we tackle items that we feel we can achieve i.e. that a community member feels they can contribute to. Now what I have identified below is the same list we had for Sprint 12 discussion which was deemed suitable for community to approach. Some have been tackled some haven't... should these be 're-nominated'? Concept | Actionable Task | Github Issue | Assigned | Complexity | Sprint | Comment ------------ | ------------- | ------------- | ------------- | ------------- | ------------- | ------------- Emails | Test Coverage | #7299 | Core/Community | Medium | 12, 13 | Emails | ~~Attachments Should not be Sending on Reply~~ | #7071 | Community | Low | 12 | DONE Emails | Inline Images not shown in received/sent Emails | #6470 | Core/Community | Medium | 12, 13 Emails | ~~Admin can not edit User's Mail Accounts~~ | #7249 | Community | Medium | 12 | DONE Emails | Incoming IMAP mail issues | #7186 | Community | Medium | 12, 13 | Needs help troubleshooting Themes | Add in Max 3 columns Support | #3310 | Core/Community | Medium | 13 | Themes | Reduce Padding Edit/Detail/List | #7373 | Core/Community | Low | 13 | Misc | Include a Composer section in Documentation | https://github.com/salesagility/SuiteDocs/issues/273 | Core/Community | Low | 12, 13 | Misc | Develop PRs | #3007, #6602, #6672 | Community | - | - | Items still allocated to the Core (potentially Community too) team Concept | Actionable Task | Github Issue | Assigned | Complexity | Sprint | Comment ------------ | ------------- | ------------- | ------------- | ------------- | ------------- | ------------- Emails | ~~Delete Emails~~ | #3727 | Core | - | 12 | DONE Emails | See Attachments on Non Imported Emails | #5190 | Core | High | 12 | Moved to 13 as it is a tough one... Emails | Can’t filter on multiple Inboxs/Folders | #7279 | Core | High | 12, 13 | Emails | ~~Group Email Accounts Not Respecting Reply to Admin restriction~~ | #6992 | Core | Medium | 12 | IN REVIEW Emails | Attachments Not being Sent (multiple areas) | #6968, #5520, #5552, #2174 | Core/Community | High | 12, 13 | Emails | Differences between Imported/Non Imported Email Views | #4881 | Core | Medium | 12, 13 | Emails | ~~Auto Importing Not Working~~ | #6866, #6534 | Core | Medium | 12 | DONE Emails | Bulk Actions is disabled | #7298 | Core | Low | 12 | In Progress Themes | Update documentation on customising Themes | #5440, https://github.com/salesagility/SuiteDocs/issues/291 | Core | Low | 12, 13 | Themes | List View: Mirror Subpanels + on smaller screens | | Core | Medium | 13 | Misc | ~~Confirm that issue was resolved regarding ElasticSearch issue on shared hosting~~ | | Core | Medium | 12 | UNABLE TO TEST Misc | Update documentation that Shared Hosting should be OK with ElasticSearch | | Core | Low | 12, 13 | Misc | Create a Migration Guide to help others to upgrade | https://github.com/salesagility/SuiteDocs/issues/292 | Core/Community | Low | 12, 13 | Lets make a group discussion for this Misc | Update documentation to state that GDPR is not mandatory option | https://github.com/salesagility/SuiteDocs/issues/293 | Core | Low | 12 | Misc | ~~Popup Studio and Calendar don't auto-close~~ | #3756 | Core/Community | Low | 12, 13 | IN REVIEW Misc | ~~housekeep session files~~ | #3157 | Core | Medium | 12, 13 | IN REVIEW Misc | Test Suite Improvements | #7344 | Core/Community | Medium | 12, 13 | ON GOING We will also be pulling in High Priorities into this sprint as these should always be tackled ASAP. Retrospect this housekeeping is abit fidgetity.. perhaps it better just to identify the issues people want to nominate and move them into the sprints backlog - the To Do column will be what has been allocated out and people have identified their interest in tackle that said issue? https://github.com/salesagility/SuiteCRM/projects/7 I feel comfortable that we still have a lot of things to tackle in this sprint but we should be keep this discussion open to improve our processes & gain feedback :+1:

deekerman

2026-02-20 16:10:11 -05:00

closed this issue
added the
Type:Discussion
label

deekerman commented

2026-02-20 16:10:12 -05:00

Author

Owner

@samus-aran commented on GitHub (Jul 1, 2019):

As part of the review it would also be great to highlight the amazing contributions made by our dev community...

repo:salesagility/SuiteCRM is:pr created:2019-06-01..2019-06-30 -label:dependencies label:"Community Contribution"

You can use this to help highlight the activity in the past month. 53 Prs made by the community! Amazing stuff. 🎉 This is actually the highest we have seen. But lets break this down and see if what developers are raising correlates to what was highlighted in the last sprint.

If we view the “closed” (but not merged) Prs, this is usually Prs that were the wrong branch, needed to start from scratch again or where not valid etc. So usually we don’t pick those up.. there was 9 of them.

From what we can see most of the Prs raised were all about the automated testing (thank you @connorshea & @lazka) & a few from @604media (already highlighted they did take on sprint tasks) as well as other bug fixes. @eggsurplus provided fixes for SecuritySuite, thanks jason for your continuous maintenance!
Also to highlight @re8260 for your Prs – its great to see issues raised and resolved by same person 👍

Then we look at the merged Prs:

repo:salesagility/SuiteCRM is:pr is:merged merged:2019-06-01..2019-06-30 -label:dependencies label:"Community Contribution"

This equals to 34! Mostly are about automated testing, a range of fixes for sub themes, reports, emails (not in sprint) and other misc. Thanks for these!

So as we can see there is ALOT on the automated testing which obviously helps developers who contribute get accurate feedback from the test framework, as well as speeds up time on this PR blocker process.

But is this what stopping more community members picking up highlighted issues in the sprint? I know we have partners & third party service providers of SuiteCRM who must run into these core issues that people have raised… It would be great to hear from them…

Thanks to all the community contributors and giving back to the project that so many people use!

@samus-aran commented on GitHub (Jul 1, 2019): As part of the review it would also be great to highlight the amazing contributions made by our dev community... repo:salesagility/SuiteCRM is:pr created:2019-06-01..2019-06-30 -label:dependencies label:"Community Contribution" You can use this to help highlight the activity in the past month. **53** Prs made by the community! Amazing stuff. :tada: This is actually the highest we have seen. But lets break this down and see if what developers are raising correlates to what was highlighted in the last sprint. If we view the “closed” (but not merged) Prs, this is usually Prs that were the wrong branch, needed to start from scratch again or where not valid etc. So usually we don’t pick those up.. there was 9 of them. From what we can see most of the Prs raised were all about the automated testing (thank you @connorshea & @lazka) & a few from @604media (already highlighted they did take on sprint tasks) as well as other bug fixes. @eggsurplus provided fixes for SecuritySuite, thanks jason for your continuous maintenance! Also to highlight @re8260 for your Prs – its great to see issues raised and resolved by same person :+1: Then we look at the merged Prs: repo:salesagility/SuiteCRM is:pr is:merged merged:2019-06-01..2019-06-30 -label:dependencies label:"Community Contribution" This equals to **34**! Mostly are about automated testing, a range of fixes for sub themes, reports, emails (not in sprint) and other misc. Thanks for these! So as we can see there is ALOT on the automated testing which obviously helps developers who contribute get accurate feedback from the test framework, as well as speeds up time on this PR blocker process. *But* is this what stopping more community members picking up highlighted issues in the sprint? I know we have partners & third party service providers of SuiteCRM who must run into these core issues that people have raised… It would be great to hear from them… Thanks to all the community contributors and giving back to the project that so many people use!

deekerman commented

2026-02-20 16:10:13 -05:00

Author

Owner

@gunnicom commented on GitHub (Jul 1, 2019):

But is this what stopping more community members picking up highlighted issues in the sprint?

I did not know about the sprint taking place now.

@gunnicom commented on GitHub (Jul 1, 2019): > But is this what stopping more community members picking up highlighted issues in the sprint? I did not know about the sprint taking place now.

deekerman commented

2026-02-20 16:10:13 -05:00

Author

Owner

@samus-aran commented on GitHub (Jul 1, 2019):

But is this what stopping more community members picking up highlighted issues in the sprint?

I did not know about the sprint taking place now.

Absolutely right! I checked back in the previous sprint and you weren't mentioned...

I don't want to keep on mentioning the same people in each sprint planning so hopefully having the pinned issue will help. Any one have any other suggestions?

BTW welcome aboard @gunnicom 😉

@samus-aran commented on GitHub (Jul 1, 2019): > > But is this what stopping more community members picking up highlighted issues in the sprint? > > I did not know about the sprint taking place now. Absolutely right! I checked back in the previous sprint and you weren't mentioned... I don't want to keep on mentioning the same people in each sprint planning so hopefully having the pinned issue will help. Any one have any other suggestions? BTW welcome aboard @gunnicom :wink:

deekerman commented

2026-02-20 16:10:13 -05:00

Author

Owner

@connorshea commented on GitHub (Jul 2, 2019):

My main blocker is that I can only focus on so many things at a time :)

Generally, I think updating our automated testing processes helps everybody else get more work done (less flaky tests => less waiting for someone to re-run the tests, faster tests => less waiting for feedback, making it easier/possible to run the tests locally, and providing better documentation => less need to wait on Travis to see if tests pass and less test runs in the CI queue), so that's what I've been focusing on mostly right now.

It also helps that the tests have a lot of low-hanging fruit in terms of fixes :D

@connorshea commented on GitHub (Jul 2, 2019): My main blocker is that I can only focus on so many things at a time :) Generally, I think updating our automated testing processes helps everybody else get more work done (less flaky tests => less waiting for someone to re-run the tests, faster tests => less waiting for feedback, making it easier/possible to run the tests locally, and providing better documentation => less need to wait on Travis to see if tests pass and less test runs in the CI queue), so that's what I've been focusing on mostly right now. It also helps that the tests have a lot of low-hanging fruit in terms of fixes :D

deekerman commented

2026-02-20 16:10:13 -05:00

Author

Owner

@samus-aran commented on GitHub (Jul 2, 2019):

@connorshea I was hoping we had made it plainly obvious how much we have appreciated all your time n effort with the automated test. 👏👏👏 My question was about what was the major blockers of other community drv members face and does having the flakey tests stable be the only cure to get more bug fixes contributed?

@samus-aran commented on GitHub (Jul 2, 2019): @connorshea I was hoping we had made it plainly obvious how much we have appreciated all your time n effort with the automated test. 👏👏👏 My question was about what was the major blockers of *other* community drv members face and does having the flakey tests stable be the only cure to get more bug fixes contributed?

deekerman commented

2026-02-20 16:10:13 -05:00

Author

Owner

@connorshea commented on GitHub (Jul 2, 2019):

Oh, don't worry I understood that! :) I just wanted to reply since I saw that only gunnicorn had responded, and hoped it'd push others to respond as well :P

@connorshea commented on GitHub (Jul 2, 2019): Oh, don't worry I understood that! :) I just wanted to reply since I saw that only gunnicorn had responded, and hoped it'd push others to respond as well :P

deekerman commented

2026-02-20 16:10:13 -05:00

Author

Owner

@samus-aran commented on GitHub (Jul 26, 2019):

Closing. Sprint 15 is available. The release associated to this sprint will be 7.10.18 & 7.11.7

@samus-aran commented on GitHub (Jul 26, 2019): Closing. Sprint 15 is available. The release associated to this sprint will be 7.10.18 & 7.11.7