Comments
-
If you add a Confluence under the same domain, it will become linked to your Jira automatically. It's one of the reasons Cloud is "software as a service" - automation of linkages is something people don't want to have to think about.
-
They will have put those restrictions on their pages, and for good reasons. It sounds like you are trying to control everything, which is simply not what Confluence is designed for. It's for working together, not having an editor control everything manually. If you insist on doing this sort of thing, you're going to need…
-
I'm afraid this is what you signed up for when you bought into Cloud - latest updates rolled out frequently and unilaterally.
-
What precisely do you want to measure when you're saying "progress"? There's lots of measures it could be, none of them are right for everyone, but we can't tell you a lot without a rule that gives us the measure. (For example "% of unresolved issues in a sprint" can be a good one. Or "number of issues in each non-closed…
-
No, your field configurations are all separate. But it sounds like you are sharing them. A change to a shared scheme will take effect everywhere the scheme is used. It sounds like you need to split the field configurations up so you can remove some fields from the issues.
-
I think you are getting roles and groups confused. * A group is a collection of users * A role is a container for users and groups that crosses all projects. For example, I can set up three projects, A, B and C, and one role like "developer". I can then put different people into the "developer" role in A, B and C.…
-
You can not use an expired licence for any version of Jira released after the end date of your licence. You must renew the licence or buy a new one to use a version that was released after the expiry on the old licence.
-
What do you mean by "affect"? It's a verb that is very vague, especially in terms of Jira. Edit? Create? Comment? Link? Transition? All those actions "affect" an issue. Could you check your permissions - do you have the project permissions to do whatever you mean by "affect"?
-
There's no way of knowing from that one snippet of log (a java "null pointer exception" is a very general error and often just the last point in a chain of errors, despite coming out first in logs). What does the rest of the log say the error is down to?
-
You get a build success, so I can only assume something is not working in your add-on when you test it, and you suspect it's down to one of the warnings or errors in the log? Could you explain what the fault is? Or are you just worried about the block of spring errors?
-
Confluence provides limited access to places the anonymous user might find useful - search, the dashboard, etc. The only way to block that access would be to do it at the web-server side. If you have a proxy, you can block the non-space pages. It's not particularly useful to do so though.
-
No, as doing reporting from a dump is the second worst way you can do reporting. You're probably importing the data into a generalised tool like excel to do this, and I know from bitter experience that the error rate in excel sheets is between 90 and 99% if they've been built by a human rather than code. When I see a…
-
That can do it, but there's also scripting add-ons, reporting add-ons and other field add-ons that might do it. I'd use ScriptRunner, but I'm biased because I work there and hence use it for everything.
-
The label field is a bounded list of objects.
-
You need code (i.e. some form of add-on) to do this.
-
"import" - not really, but you can easily use "move". Search for the issues to move, then use bulk-edit on the result, one of the options will be "move issues"
-
Oh, I do it all the time, still!
-
You don't need to. You should be adding JSD to your existing instance. If you don't install it there, then you won't get any linking functionality beyond the simple Jira to Jira linking. You won't be able to draw developers into issues, automate responses and updates etc.
-
None of those apply really. There's a link in the menu of the service desk issue. Click it, and it will ask what project and what to copy from the current issue.
-
If you get a search right in basic mode, and then click over to advanced, it will keep the JQL so you can see what the basic search is doing. At a guess though, I'd say it's about using non-alpha characters. Try replacing AND Sprint =Sprint 2018.12 with AND Sprint = "Sprint 2018.12"
-
Well, the file is broken and needs fixing, no matter how it got that way. Could the loss of disk space have corrupted it?
-
Someone editing it. That file is only read when starting up, so someone may have changed it weeks or months ago, but you only found a problem when restarting Confluence the next time.
-
Your screenshot does look like it's a simple macro on a page. I'm not sure it was the "child pages" macro, as an upgrade would not have removed it from the pages. There are some macros which the upgrade process would remove because they don't work at all on the newer version, but I'm not sure that is what has happened.…
-
You need your admins to fix the mistakes they've made, to prevent more data becoming wrong, then you can fix the existing damaged data as a second exercise. To prevent more damage * Do a quick-fix, and remove the resolution from all screens in the system. * Then look at every transition from open to closed (this will…
-
Ok, but that means your "series" is not looking at either of the searches you've given us. You'll need to find the one it is looking at. I suspect it might be one of the service desk queues.
-
The design intention is that the Agent would use "create linked issue", targetting the project the development should go into.
-
Not a clue what "MIS on TAT" might be, but it sounds like it needs to be written properly. Either build reports for Jira, or get that system to ask better questions than just "dump a huge pile of issue data"
-
It does show up, unless you're on a really old version of Jira where labels was still a separate add-on or was still in the process of being properly merged in. Should be there from version 5 if memory serves.
-
There's a wonderful technology called "reading the previous discussion" too.
-
Go to search -> export