Submitted pull request for Slack plugin to include report files, no response after 4 mo

Hi,
I submitted a pull request for the Slack plugin back in December 2019 that would support sending configured report files to the slack channel (making the plugin a lot more useful imho), but no one has responded to my pull request. It would be nice to get a response eventually on the pull request.
Thanks,
Jeanie

@duyluong and @devalex88 do you think you guys can take a look at this pull request? I submitted it back in December and haven’t heard anything. Thanks.

  • Jeanie
1 Like

or if I should submit my branch as a separate plugin for the store, that’s ok too… basically, I cannot use my plugin currently on azure devops pipeline bc it is not installed from the store, so I need to fix that somehow…

@jeanie.conner

You can build your own plugin and put it to the Plugins/platform folder if you have KSE or KRE license.

We saw your pull request. The main purpose is sending report files: html, csv, pdf to slack channels. We will evaluate your PR later but the UI should need some changes to persist with Katalon Studio UI style.

ok - thanks! I wasn’t even sure if someone noticed it bc I didn’t get any response. Thanks, I got my plugin working now on Azure, I didn’t know it had to be in the Platform folder for it to auto-install.

1 Like

Can you share how I can do the same? We have requested a requirement for this but Katalon doesn’t seem to think it’s important.

Can we get an update on this? is this change added? PR approved? This is a great idea even my stakeholder are asking for.

Is there any way you can create this for me to use? Katalon seems to not care about approving your PR

1 Like

for your action , may be , @nghi.phan

1 Like

Hi @ashraf.madina

Thanks for your feedback on the Feature Request flow, you already submitted the feature via support ticket 00017608 which was raised successfully to the Product Team.

We sincerely apologize for the delay in releasing this feature. The team is carefully considering various factors, including user demand and technical feasibility, to ensure we make the best decision moving forward.

Rest assured, your voice has been heard, and the team is actively researching and developing this implementation. We’ve emphasized its priority again to them and will keep you and everyone else updated as soon as it’s launched into production.

Thanks for your understanding and support!

Best regards,

Eve.