Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-3012

you should be able to set up a non-utf8 db via the ui

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      currently we "require" that any database configured be using UTF-8.

      however:
      1. you can do a backup / restore to a non-UTF-8 db
      2. you can manually edit the config.xml and fecru will start up (just with warnings)
      3. if you are only using fisheye, this isnt really an issue and shouldnt affect you.

      we should make it clear that the database is not UTF-8 when setting it up in the UI, but we should still allow the user to save the settings.

            [FE-3012] you should be able to set up a non-utf8 db via the ui

            Atlassian Update – 5 October 2018

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Regards
            Marek Parfianowicz
            Fisheye/Crucible TL

            Marek Parfianowicz added a comment - Atlassian Update – 5 October 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Regards Marek Parfianowicz Fisheye/Crucible TL

            this case should be escalated to High because during the database connection setup step, I'm getting error message "The database is not using Unicode. FishEye and Crucible require that the database uses a UTF8 encoding to support internalization"

            So i cannot move forward without resolving this issue.

            Aiping Zhang added a comment - this case should be escalated to High because during the database connection setup step, I'm getting error message "The database is not using Unicode. FishEye and Crucible require that the database uses a UTF8 encoding to support internalization" So i cannot move forward without resolving this issue.

            how about if i'm also using Crucible?

            Aiping Zhang added a comment - how about if i'm also using Crucible?

              Unassigned Unassigned
              gcrain Geoff Crain (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: