Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-6709

Options to disable auto creating Confluence space with creating JIRA Service Desk project

XMLWordPrintable

    • 0
    • 1
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Atlassian Update – 4 March 2021

      Hi everyone,

      Thank you for your interest in this issue.

      The option to configure Confluence knowledge base space creation was shipped in JSM 4.14.

      To manage this setting as a Jira administrator:

      1. Choose Administration > Applications. Scroll down to the Jira Service Management section and choose Configuration.
      2. In the Knowledge base section, you can change whether a Confluence knowledge base space is automatically created when creating a service project.

      Kind regards,

      Charlie

      Jira Service Management, Server & Data Center

      Problem Definition

      Currently , when creating a new JIRA Service Desk project , it will automatically create a Confluence space when the instance have Confluence application installed/linked.

      Suggested Solution

      Options to create or not to create the space.

      Why this is important

      Sometimes the JIRA Service Desk not required to have a knowledge base , so creating a space is not required.

      Workaround

      Application Link (Authentication Methods) does the trick, using OAuth is unable to replicate the behavior. You can refer to this documentation on the differences between OAuth and OAuth Impersonation. Using the bug as a workaround will causing you unable to create new space in Confluence from JIRA. If the project admin is able to access to Confluence to create new space and update Service Desk Project KB configuration to space manually, then OAuth shall be workable in this scenario.

        1. Knowledge base configuration.png
          Knowledge base configuration.png
          34 kB

            [JSDSERVER-6709] Options to disable auto creating Confluence space with creating JIRA Service Desk project

            Deema Sargent added a comment -

            Was this not fixed for Cloud yet? I don't see the option to disable it. 

            Deema Sargent added a comment - Was this not fixed for Cloud yet? I don't see the option to disable it. 

            Charlie Marriott added a comment - - edited
            Atlassian Update – 4 March 2021

            Hi everyone,

            Thank you for your interest in this issue.

            The option to configure Confluence knowledge base space creation was shipped in JSM 4.14.

            To manage this setting as a Jira administrator:

            1. Choose Administration > Applications. Scroll down to the Jira Service Management section and choose Configuration.
            2. In the Knowledge base section, you can change whether a Confluence knowledge base space is automatically created when creating a service project.

            Kind regards,

            Charlie

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - - edited Atlassian Update – 4 March 2021 Hi everyone, Thank you for your interest in this issue. The option to configure Confluence knowledge base space creation was shipped in JSM 4.14 . To manage this setting as a Jira administrator: Choose  Administration > Applications . Scroll down to the  Jira Service Management  section and choose  Configuration . In the  Knowledge base  section, you can change whether a Confluence knowledge base space is automatically created when creating a service project. Kind regards, Charlie Jira Service Management, Server & Data Center

            Funda Uezer added a comment -

            Hello,

            Currently we (Robert Bosch GmbH) are using 3.16.8 Version and we are still facing this issue.

            The workarround is not useful for us. So it would be great if we get a longterm solution for it (possibility to disable the creation of spaces).

            Thank you!

             

            Funda Uezer added a comment - Hello, Currently we (Robert Bosch GmbH) are using 3.16.8 Version and we are still facing this issue. The workarround is not useful for us. So it would be great if we get a longterm solution for it (possibility to disable the creation of spaces). Thank you!  

            Mandeep Singh added a comment - - edited

            Thanks for your feedback, we will review the current experience - marking this under consideration.

            Mandeep Singh added a comment - - edited Thanks for your feedback, we will review the current experience - marking this under consideration.

            Branislav Slavik added a comment - - edited

            Dear ashubovych,

            So, based on your statement a.:

            we have made an agreed decision that this is a suggestion, as a. this is an existing behaviour

            This cannot be a "Suggestion". "Suggestions" are made when some behavior is missing and we would "suggest" having/seeing it there. And, you have just agreed that this behavior/problem/bug exists. I would just add on top of that, that it is because of a sloppy way of programming and/or introduction of a "new" feature.

            As of your statement b.:

            and b. not all the customers might want this behaviour changed.

            I don't see the problem here. Let's make the "Auto-creation" a default behavior. This way, the current behavior won't change for anybody.

            The problem/bug here is the fact, that there is no way to turn the "Auto-creation" feature OFF.

            I don't understand why you (Atlassian) would introduce an "automatic" feature without a possibility to switch if off on purpose. Especially when the logic and implementation could be as simple as:

            IF there is some variable - for example jsd.kb.autocreate set (for example in jira-config.properties) to false, THEN do nothing, ELSE "work as usual"...

            To react on the following statement:

            I was unable to find the page or a document describing this behaviour, so just backtracked the internal ticket from the code. This automated behaviour was seemingly introduced in JSD 3.3.0 and has been there ever since.

            I understand that this feature is not a new one. We, as customers - Commerzbank A.G., started implementing JSD only recently with version 4.5.3. We noticed this bug and immediately reported it, so it can be fixed. Especially when the "fix" could be as simple as one "if condition" somewhere in the code of this feature.

            The fact that the "feature" is there since version 3.3.0 and is still not documented shows and points out your (Atlassian) sloppiness when introducing it even more.

            So, again, to conclude, due to the reasons pointed out above, this is a bug and not a suggestion. Please be reasonable. Admit that mistake(s) were made and fix it.

            Best regards,
            Branislav Slavik

            Branislav Slavik added a comment - - edited Dear ashubovych , So, based on your statement a. : we have made an agreed decision that this is a suggestion, as a. this is an existing behaviour This cannot be a "Suggestion". "Suggestions" are made when some behavior is missing and we would "suggest" having/seeing it there. And, you have just agreed that this behavior/problem/bug exists. I would just add on top of that, that it is because of a sloppy way of programming and/or introduction of a "new" feature. As of your statement b. : and b. not all the customers might want this behaviour changed. I don't see the problem here. Let's make the "Auto-creation" a default behavior. This way, the current behavior won't change for anybody. The problem/bug here is the fact, that there is no way to turn the "Auto-creation" feature OFF. I don't understand why you (Atlassian) would introduce an "automatic" feature without a possibility to switch if off on purpose. Especially when the logic and implementation could be as simple as: IF there is some variable - for example jsd.kb.autocreate set (for example in jira-config.properties ) to false, THEN do nothing, ELSE "work as usual"... To react on the following statement: I was unable to find the page or a document describing this behaviour, so just backtracked the internal ticket from the code. This automated behaviour was seemingly introduced in JSD 3.3.0 and has been there ever since. I understand that this feature is not a new one. We, as customers - Commerzbank A.G., started implementing JSD only recently with version 4.5.3. We noticed this bug and immediately reported it, so it can be fixed. Especially when the "fix" could be as simple as one "if condition" somewhere in the code of this feature. The fact that the "feature" is there since version 3.3.0 and is still not documented shows and points out your (Atlassian) sloppiness when introducing it even more. So, again, to conclude, due to the reasons pointed out above, this is a bug and not a suggestion. Please be reasonable. Admit that mistake(s) were made and fix it. Best regards, Branislav Slavik

            moofoo (Inactive) added a comment - - edited

            0e3305ce2d55

            After discussing this with our product managers, we have made an agreed decision that this is a suggestion, as a. this is an existing behaviour and b. not all the customers might want this behaviour changed.

            I was unable to find the page or a document describing this behaviour, so just backtracked the internal ticket from the code. This automated behaviour was seemingly introduced in JSD 3.3.0 and has been there ever since.

            Cheers,
            Jira Service Desk team

            moofoo (Inactive) added a comment - - edited 0e3305ce2d55 After discussing this with our product managers, we have made an agreed decision that this is a suggestion, as a. this is an existing behaviour and b. not all the customers might want this behaviour changed. I was unable to find the page or a document describing this behaviour, so just backtracked the internal ticket from the code. This automated behaviour was seemingly introduced in JSD 3.3.0 and has been there ever since. Cheers, Jira Service Desk team

            Branislav Slavik added a comment -

            Hi Artem,

            The Support engineer Danson Koh changed this to a Bug based on my explanation/reasons provided in the SDS-47436 ticket. I will copy it also here.

            I understand that you choose what you implement and what not. What I don't understand is the way of thinking of the Atlassian product manager(s).

            They decided to implement a feature without any on/off switch. When we, as clients and users, asked for that switch which should be a standard, the reply is - it's a new feature, maybe we implement it, maybe not. We'll see... :shrug:

            In addition to this, there is the fact, that we are actually using a bug in one of the two Authentication methods available in Application link setup as a "workaround".

            So, if this bug is fixed in some newer version and we won't know about it, we can create a mess in our instance of Confluence. And on top of this, we will lose any way how to prevent the automatic creation.

            Hence, I would say, that JSDSERVER-6709 is not a "New Feature" request, but it's a "Bug" that points out a sloppy way of programming and implemetation of the "Automatic knowledge base creation" feature.

            The answer from Danson Koh was:

            I do understand your point of view. Yes, I agree with you, this should be considered as a bug instead of a feature request. I had just done a quick check internally and we had updated the ticket as a bug.

            So, please revert your changes as it was agreed that this is a bug report and not a Suggestion.

            Branislav Slavik added a comment - Hi Artem, The Support engineer Danson Koh changed this to a Bug based on my explanation/reasons provided in the SDS-47436 ticket. I will copy it also here. I understand that you choose what you implement and what not. What I don't understand is the way of thinking of the Atlassian product manager(s). They decided to implement a feature without any on/off switch. When we, as clients and users, asked for that switch which should be a standard , the reply is - it's a new feature, maybe we implement it, maybe not. We'll see... :shrug: In addition to this, there is the fact, that we are actually using a bug in one of the two Authentication methods available in Application link setup as a "workaround" . So, if this bug is fixed in some newer version and we won't know about it, we can create a mess in our instance of Confluence. And on top of this, we will lose any way how to prevent the automatic creation. Hence, I would say, that JSDSERVER-6709 is not a "New Feature" request, but it's a "Bug" that points out a sloppy way of programming and implemetation of the "Automatic knowledge base creation" feature. The answer from Danson Koh was: I do understand your point of view. Yes, I agree with you, this should be considered as a bug instead of a feature request. I had just done a quick check internally and we had updated the ticket as a bug. So, please revert your changes as it was agreed that this is a bug report and not a Suggestion.

            moofoo (Inactive) added a comment -

            Hi,

            This behaviour was designed and documented as it is - it does not behave any different to what was described, so from that perspective it is not a bug but a documented (yet, totally true, with a bad user experience) behaviour with no documented workaround.

            We shall pick it up to our roadmap and prioritise based on the interest to this.

            Cheers,
            Jira Service Desk team

            moofoo (Inactive) added a comment - Hi, This behaviour was designed and documented as it is - it does not behave any different to what was described, so from that perspective it is not a bug but a documented (yet, totally true, with a bad user experience) behaviour with no documented workaround. We shall pick it up to our roadmap and prioritise based on the interest to this. Cheers, Jira Service Desk team

            Branislav Slavik added a comment -

            Hello,

            It would be really great if you could deliver this feature soon.

            We already have JIRA and Confluence instances running in our company. We don't want the Confluence KB space to be automaticall created every time we create a new project in Service Desk. A lot of our clients already have Confluence spaces and we want to add them manually when this is necessary and not to delete them all the time.

            Hope this gets delivered soon.

            Best regards,
            Branislav Slavik

            Branislav Slavik added a comment - Hello, It would be really great if you could deliver this feature soon. We already have JIRA and Confluence instances running in our company. We don't want the Confluence KB space to be automaticall created every time we create a new project in Service Desk. A lot of our clients already have Confluence spaces and we want to add them manually when this is necessary and not to delete them all the time. Hope this gets delivered soon. Best regards, Branislav Slavik

              bornatowski Bartosz Ornatowski
              dkoh Danson (Inactive)
              Votes:
              10 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: