Jira Assistant add-on not found in firefox marketplace
From README.md I understand JiraAssistant is also supported for Firefox. However, the link to the mozilla add-ons marketplace (https://addons.mozilla.org/en-US/firefox/addon/jira-assistant/) takes you to an error page.
Is the firefox version still supported? I could not find any information stating the opposite (just two similar issues where it seems the problem was fixed)
To All, Firefox add-on store has lots of restrictions and it gives me lots of trouble in maintaining it. One out of it is they keep asking questions and if I do not reply on time they disable the add-on, after which I will have to answer and republish a new build package.
So I decided not to maintain the extension anymore for firefox throught add-on store. I am planning to build a external package and host it separately for firefox. I will have to check the feasibility for that and once done I will update the details in this ticket.
At the mean time I would like to know if users are willing to install the package if it is not from add-on store. You can leave your thoughts here about this.
@shridhar-tl This is a good idea!
Hi @Hunternnm , @mgab , Now add-on for Firefox is available for download from the following URL. Anyone willing to install it can do so from the following Url. Access the following link from Firefox and it should automatically install the Addon. If it did not automatically install it then you can download it and then drag and drop the downloaded file to Firefox and it should get installed. Incase if any one face any issue please post it here so that I will update the documentation accordingly to help others from facing the same issue again.
@shridhar-tl hmm, on ubuntu 18.04 + Firefox 61.0.1 after clicking to integrate button, I get an error message -
Action error One or more of the actions failed
Hi @Hunternnm , Please check the console error and provide the details.
@all - Anyone facing any issues, please check the console and if their any errors, please provide them.
Their were lots of updates since this issue was reported and hence I hope this issue would have got resolved with the updates. If anyone is still facing any issue, I would suggest to open a new ticket with appropriate details.