Issues
- vendors - Unable to use "dashes" "-" in search barZNTA-2056Resolved issue: ZNTA-2056Former user
- [regression] Project 'Search and Replace' header not sized correctlyZNTA-1778Resolved issue: ZNTA-1778Former user
- Backwards compatibility broken for fileTypes parameterZNTA-1248Resolved issue: ZNTA-1248Sean Flanigan
- "The email already taken" & "The username already taken" appearing twice in OpenID New User Login PageZNTA-1208
- Regression: cannot connect Fedora / OpenID account (NPE), various changes not savedZNTA-1174Resolved issue: ZNTA-1174Sean Flanigan
- Yahoo login indicates "Login failed" despite login successZNTA-1112Resolved issue: ZNTA-1112Carlos Munoz
- Cannot delete a version in 3.8.2ZNTA-953Resolved issue: ZNTA-953Former user
- Cannot download document offline .po, exception occursZNTA-940Resolved issue: ZNTA-940Former user
- Reset password feature fails on session closedZNTA-931Resolved issue: ZNTA-931Armağan Ersöz
- Changing user email address redirects to invalid pageZNTA-871Resolved issue: ZNTA-871Former user
- Reset Password feature not inserting key into databaseZNTA-870Resolved issue: ZNTA-870Former user
- Regression: Generic OpenID (livejournal) does not work in 3.9ZNTA-867Resolved issue: ZNTA-867Carlos Munoz
- [Regression] Admin monitoring button has no linkZNTA-803Resolved issue: ZNTA-803Former user
- [Regression] Login page fields are not rendered after activationZNTA-720Resolved issue: ZNTA-720Former user
- Admin Manage Search feature UI brokenZNTA-715Resolved issue: ZNTA-715Former user
- [Regression] Cannot download an offline .poZNTA-671Resolved issue: ZNTA-671
- Glossary copy buttons don't workZNTA-612Resolved issue: ZNTA-612
- Error (exception) on project page after removing an aliasZNTA-608Resolved issue: ZNTA-608Former user
- Glossary push doesn't work if transLang not specifiedZNTA-18Resolved issue: ZNTA-18Former user
19 of 19
We couldn't connect to that issue
Make sure that this issue actually exists in that project. If it does, try again in a few minutes. If you still can't link to the issue, contact your Jira admin.