Closed ricardorlg-aval closed 4 years ago
@wakaleo any comments on this, or can this PR be merge.
Thanks for reminding me @ricardorlg-aval
@wakaleo Please can you confirm the Serenity-Jira Plugin version, which has this fix. Thanks.
It hasn't been released yet, I will probably do a release later this week or next week.
Thanks much @wakaleo Please can you update here, once done.
@wakaleo Please can you confirm if the fix is released now. If this would take time, we are ok to role back to older JIRA version. Please advise JIRA version with which the below serenity-jira-plugin:1.12.0 would work.
serenity-jira plugin used in our project: jira: "net.serenity-bdd:serenity-jira-plugin:1.12.0", jirarequirements: 'net.serenity-bdd:serenity-jira-requirements-provider:1.12.0'
This has not been released yet.
@wakaleo If it's not released, please advise JIRA version with which the serenity-jira-plugin:1.12.0 would work.
I don't know, I haven't been keeping track of the JIRA API changes.
Ok thanks @wakaleo When would the change be released, please?
@wakaleo Any update on this, please?
May I ask when is the possible release date for this solution? @wakaleo
@wakaleo Just another reminder. I also just came across this. It would be nice to know the timeline for this.
I too am having this issue. Would love the fix to be available.
@wakaleo is this not released yet?
No, not yet. I don't have a JIRA instance handy to test it against.
I test It against company JIRA. should I test it again, just to see if it's still working?
Did you do a local build of the whole library?
yes I did it, and run my project using the snapshot, and it works, I will do it again and let u know.
OK, if you can check again with the latest snapshot I will do a release.
Is this going to get released any time soon?