Xorcist Posted January 15, 2016 Report Share Posted January 15, 2016 So it appears if there are special characters in your AxoSoft password (which works just fine logging into AxoSoft) will result in Plastic not being able to connect to AxoSoft. I used to have !, @, and # in my password and kept getting an error on trying to connect. Changing my password in AxoSoft to only include letters and numbers allowed Plastic to connect, this seems like a bug in the string handling from the Plastic side of things. Can someone look into this, I tend to like to have special characters in all my passwords. P.S. On a separate note, is there anyway to filter issues per project, release, or sprint? We often work on multiple projects at once, and it's getting a little hard to manage creating a branch from an existing task. Link to comment Share on other sites More sharing options...
manu Posted January 21, 2016 Report Share Posted January 21, 2016 Hi there! I've tested it and it seems there's a problem with the '#' symbol. '!' and '@' seems to be working fine for me. Link to comment Share on other sites More sharing options...
Xorcist Posted January 22, 2016 Author Report Share Posted January 22, 2016 If a Username/Password grant type is being used against their API to authenticate, and the URI is not being encoded, the # character is probably being interpreted as a fragment (rather than the literal # character). Search for fragment here: https://en.wikipedia.org/wiki/Uniform_Resource_Identifier I have not tested their API myself, so I can't say which side the fault is on, but I do know my password works fine when logging into our AxoSoft instance. P.S. One other thing I noticed, is that all new branches created off Axosoft tasks want to start the branch name with "def", so defects become "defdef#", incidents become, "definc#", features become "deffeat#", etc. Is there a way to remove that extra "def" prefix from the start of the branch name? Maybe allow for a custom prefix similar to the way the JIRA plugin works. Link to comment Share on other sites More sharing options...
Xorcist Posted February 9, 2016 Author Report Share Posted February 9, 2016 Any updates on this item? Link to comment Share on other sites More sharing options...
manu Posted February 10, 2016 Report Share Posted February 10, 2016 Hi there, I'm sorry but the task is not scheduled yet. We'll be updating this thread once we start working on it. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.