Closed txdFrancesco closed 1 year ago
Thanks for the contribution, this will be merged with the next version of the extension.
@stefancoing Is there an indicative timeframe for the next release? Just to know if it's weeks or months away, thanks
@stefancoing Is there an indicative timeframe for the next release? Just to know if it's weeks or months away, thanks
We are releasing it together with some major internal changes so it was a bit delayed, expecting next version to be deployed some time next week.
Quick Q: Does the auto-populating of tag(s) only work if there's also a matching Project?
As I'm trying it in the latest version and unfortunately, I don't see the tag being set (tags are matching text in both Azure and Clockify). But our project does have a diff. name, so needs picking manually - wondering if that's affecting things?
Thx in advance.
Quick Q: Does the auto-populating of tag(s) only work if there's also a matching Project?
As I'm trying it in the latest version and unfortunately, I don't see the tag being set (tags are matching text in both Azure and Clockify). But our project does have a diff. name, so needs picking manually - wondering if that's affecting things?
Thx in advance.
I just tried it out and it seems to be working for me, but I usually allow the Clockify extension to create new tags if missing. Maybe you have some hidden characters or trailing spaces somewhere? Tags are also case sensitive. Anyway your problem is not really related to this PR (here I am just scraping the devOps HTML, not matching with existing tags). I suggest opening a new issue
In the azure devOps integration the tags where incorrectly selected (and therefore not inserted).
The css class scopes the tag selection to the modal (or full page) work item shown.
Tested on chrome, firefox and edge