Comments
-
You can't. The names of pages within a space must be unique. If you weren't using OnDemand, I think there's a plugin that can help, although it doesn't quite solve the problem completely. It slips my mind what it is though, sorry.
-
When you edit a page, you can click on the page title, it's an editable field like the body is.
-
They need to be covered by the permission scheme in the project. That has a list of things people can do, and the rules to choose who can do it. You probably have something like "Can be assigned issues: Role of Developer", and you have not yet added her to the role of "developer" in that project.
-
Generally, no, most plugins (if not all) look at the date the licence was generated. Doesn't matter if they are disabled or not. You may need to contact vendors to extend trial periods
-
duplicate of https://answers.atlassian.com/questions/42672474
-
Yes, the remaining estimate field is not quite a field itself. There's a pile of functionality around the "time tracking" field that the "remaining estimate" is part of. Could you outline an example of the data that is "false" and how it got there? Best bet is to look at an issue where it is "false" and tell us * What the…
-
>However, after connecting to the LB (with 2 exact Confluence with same data and pointing at same DB) SSO is not working anymore.. Are you running both at the same time? If you are, then stop. You can't do that. (The load balancing is irrelevant, you can not run two Confluence's against one database)
-
1. Components is a field for, well, defining what components an issue is related to. It's very useful to be able to select multiple components. For example, if your project is "Build a car", then the issue "Car drags to the left on test tracking" would have multiple components when it's raised - could be the tracking, the…
-
You don't. Boards are views of lists of issues, they don't hold any issues really. To "move" an issue, you change the boards. You should create your new board, and make sure it includes the issues you want to "move". Then go to the existing board, and change the filter so it no longer includes the issues.
-
Yes, but with two important points - first you need to think about how to deny them access to everything you don't want them to see (this usually means re-engineering the default permissions, as the defaults basically say "if you can log in, you can see everything), and then specifically letting them see their own issues -…
-
Minimise the use of groups, and please, please, please, use ROLES.
-
No, you need site admins to do group maintenance. I don't think that's going to change, as it's the basic principle that groups are organisational objects that may well have wider implications. But, the main point of the "roles" functionality is to delegate user access to the project administrators. Project admins can…
-
I have a feeling that auto-watch watchers are added later in the creation of the issue - your script is running at a time when the issue knows it is going to have watchers, but they aren't actually on the issue yet. A better option maybe just to ask users to unset their autowatch flag if they don't want to be added. But,…
-
OnDemand does not allow you access to the database. You'll need to use REST to get the information.
-
No. Bulk-edit really is just "do what I can do with a field, but for lots of issues at the same time". Either a field can be edited (and hence bulk edited) or they cannot be changed. The only factor is "is the field on the issue edit screen"
-
Priority is a global field, so any change to it will affect everyone. But if you go to admin -> issues -> priorities, you'll be able to upload any image you want (so find some simple icons showing numbers. I tend to look for ones that match the colours too)
-
It's a bit more than just "allows clustering" technically, but yes, you could think of the basics like that. You can think of it as an extended JIRA if you like. The front-end for the users and admins is no different, and your dev/test systems do not have to be DC for you to use them to support your production system. The…
-
From memory, there's three massive problems. One is the index - shared storage simply isn't fast enough to make it usable or even stable. Another one is the session information. I can't remember the third one with any certainty, but I think it was issues with caching and memory states being inconsistent between nodes,…
-
There have been attempts in the past, but nothing I'd hold up as even a good step towards a success. You need to move to Data Centre if you want it to work and be supported. It does work for later versions of JIRA 6, but I'd strongly recommend using JIRA 7 for it.
-
Well, to start with, that's not html at all, it's a "markup" language which uses a set of text conventions to format text. It's a lot more simple to write and structure than html, and it's actually very simple to use. The main advantage for a lot of users is the ability to simply type everything without having to click…
-
You need to log in as a customer to raise issues in the Service Desk. So I'm not sure there is any option for you here.
-
Define a filter that describes what is about to go over whatever your threshold is, and then * Subscribe to it * Use it in dashboard gadgets for a real-time display * Use it in Jelly scripts to sent out emails based on it * Ping things into IRC/Hipchat/somethingelse You've got lots of options, it's more a case of deciding…
-
The gadgets are storing their configuration. When you create them, they remember where they came from (i.e. the context in which they were created). I don't know how that's done explicitly, but I think it's in the OSGI framework stuff.
-
mmm, actually, those gadgets do depend on the base url, but they also know that they're running in Jira and therefore don't have to have it explicitly given to them. If you use them on other pages, then they need a pointer to Jira, which includes the base url...
-
Go to your account and look for the download section.
-
I suspect you need a commercial licence to see that file, as it's part of the core code (you're entitled to download the source if you have one). I suspect you'll need to amend more than that one file too - the base url is used throughout Confluence and I don't think it's changeable in just one place
-
Check your log file for errors relating to talking t remote systems.
-
Your admin access is not important, that just gives you admin rights, not space ones (admin can do everything automatically is a bad model and one that Atlassian avoid). Check the space permissions for your add/edit rights, and delete while you're there. Edit will appear as a button next to the menus and delete page in the…
-
No screenshot. (You'll also probably need several to confirm the setup, if you're only giving us one, then it's probably not enough) Anyway... Go to Admin -> Custom fields and find "Story Points" on the list. Do a full text search in the browser and confirm that there is ONLY one Story Points on the list.
-
You're going to have to examine your configuration to explain that one. Sounds like you've added two story point fields, but there's not really enough detail in your question to work with.