Comments
-
This suggests something is wrong with the index. Could you try re-indexing the project? If I am right about the index, we should see the gadget update the status to "Development"
-
* No, one of them has been added by someone. Although they might both be new - you can rename the default status to something else. I tend to avoid doing that though. * Yes. As you say, edit the workflows that use the one you don't want, swapping them to the one you want to keep, then delete the unwanted one * Shouldn't…
-
What gaps? Might be useful to give us some background on why you are asking this question? For example, are you thinking of dropping one and moving to the other? If so, what is the driver behind the idea of moving? Or are you having different teams work differently in each one and you want to look at getting them talking…
-
I would convert this to a "scripted field". Add a new scripted field, set it with the output type "number", and although I've not tested your code, at a glance, I would expect it to work with just one modification - remove the "issue = ..." line. In a scripted field, the object "issue" will already contain the current…
-
But it does follow to moved and renamed pages, it only displays page not found when a page is no longer visible, or has been deleted. I'd absolutely agree that there should be a redirect on the "page has moved" response. (Maybe a few seconds with an option to click to cancel the redirect so I can go change my bookmarks)
-
Yes, that's correct. 20 JSD for the agents, and then any customer can see the articles via the KB (and "customers" do not need licences, just accounts)
-
I'm afraid this is not a simple answer, and it depends on what you mean by "article". For Confluence on its own, there are two options: * Allow anonymous access to pages (articles). This means the entire world can read these pages, without logging in. You need no licences for anonymous people. * For pages not available to…
-
On non-next-gen boards you can put multiple status into the last column, so you can get close. Next-gen columns currently follow status 1:1 though (the status is subservient to columns), and I don't believe that will change. I doubt we will Atlassian move to more than one "done" column in Next-gen
-
Confluence does not have a function to do this, it treats each space as a single tree, without highlighting any particular pages anywhere.
-
No, the estimate field is a one-of-a-kind system field, it's not available as a custom field type.
-
That has nothing to do with upgrades. I'd suggest asking a new question if you can't find something in the software.
-
Could you explain what this has to do with Confluence?
-
I am not quite sure what you are looking for here. Atlassian, the Cloud providers, do not need to ask you anything in order to implement a Cloud environment. You sign up, the environment is built using your account as the admin, and then you then configure it to do what you want it to. Could you explain why you are asking…
-
Yes, and see https://confluence.atlassian.com/doc/upgrading-confluence-4578.html to see how.
-
There was, years ago, but Atlassian closed it with "won't do"
-
That's a complexity Jira doesn't handle off-the-shelf. I've dealt with it a couple of times though, with three totally different approaches (which can be combined) * Scripts that take a set of numeric fields, add them up, and populate the original estimate field. * Scripts that generate data for reporting. These looked at…
-
Unless the remote system embeds something in the REST call it is making that says what it is, Jira can have no way of knowing what is making the call. If you have logging at the right level, you can see what the incoming calls are in the logs. I've usually done this with a proxy in front of the service, which can also log…
-
No. It has the same base as Cloud. You can unlock fields on server, but * Do not do it, they are locked for a good reason - to stop you breaking things by doing things like changing the epic name field context * It won't do what you think it will. Your new issue type will NOT behave like an Epic. You'll get Epic Name on…
-
Nothing. You have no choice of versions, you're always on the "latest" That's the Service Desk version, not Jira which I was talking about. The Cloud answer I gave earlier still stands - versions are utterly irrelevant to you, as upgrades are handled by Atlassian on their schedule.
-
I'd strongly recommend reviewing your setup, redesigning it so issues are raised in the correct projects to start with. Moving issues between projects should never be part of a standard process.
-
There's no way to change the length without coding. To increase it, you would need to amend the database definition, and then check every line of code that handles it in Jira and its apps. Decreasing it would be easier, as you could just amend the template for the editing of the field to limit the length there. You could…
-
There is no permission for this, if you can see an issue, you can see the history. My best guess is that your "regular users" are service desk customers - they do not see the issue at all, they only see the request that sits in front of it.
-
What are you doing that makes this happen? Where is it happening?
-
I am afraid your question makes no sense. If you are "using Jira in SaaS model", you usually mean you are using Cloud. Which is not on version 3.3. Jira Cloud was based on Jira 4.something and then branched out, and the real version is now utterly irrelevant to us because it is "the latest version of Cloud Jira (within the…
-
For what?
-
It's hard to identify this from the screenshot - is it Cloud or Server? What other information is there on the issues? What is the estimation field set to?
-
What do you mean by "title"? Jira issues do not have any "title" data by default, so we need to know what you are looking at?
-
If by "hosted" you mean "Cloud" (all Jira services are "hosted" somewhere), then no, there's no restore option. It's not changed since the original 6-year-old answer.
-
What are you "unable" to migrate? What are you doing at the moment to try to "migrate"?
-
Please also remember that you can not cluster Server Jira systems in the way most of us understand "cluster". An active/standby set up is absolutely not a "cluster", but it is a very good backup/business-continuity/disaster-recovery configuration.