Comments
-
You can use "clone" from the menu options on an issue. But for a regular repeated task, it's probably better to write a very short script that uses REST to create a new issue (Pi + Cron + 20 line script, 19 lines of which is poking me on HipChat if the create fails)
-
Depends on if they've left the "contact administrators" link in the footer and or default dashboard page.
-
Yes, whoever looks after your Confluence for you.
-
Ask your administrators to put you in a group allowed to create personal spaces
-
Stuff that's nearly 10 years old really isn't of much use now. I'd strongly recommend using the API to delete - find/write an addon, or use one of the scripting options to do it over REST.
-
In theory, yes, if you have Confluence completely shut down and you do a full reindex after restarting. In practice, don't. Unless you have a very good understanding of exactly which tables you need to remove items from, you are going to break it. I'd strongly recommend using the API to delete - find/write an addon, or use…
-
So instead of doing random static and instantly obsolete reporting, you should be concentrating on writing something that draws data from your other systems and combines it with the RELEVANT Jira data (not extracting the whole lot and wasting time discarding 99% of it every time).Or just install Jira service desk and…
-
I can't do much with a vague story like that.What question(s) are you actually trying to answer?
-
Yes, 1000 at a time, it's a sensible limit. It's there for a very good reason. What he's trying to do is wrong.
-
I'd start with 16Gb and not bet on it being enough.I think the right option is to ask why you're trying to do an export that JIRA deliberately and explicitly limits, and do it properly instead of trying to bodge it.
-
It'll render your JIRA useless for a while, and then crash. It's too much, it won't cope unless you have stupid amounts of RAM allocated.
-
It's been "Boards" for around a year in Cloud. Changed when JIRA 7 was released if you're not using Cloud.
-
Nothing firm at all. I spoke to an Atlassian about it at Summit and the ability to change base-url by changing your Atlassian account settings is something they'd like to do (it won't go into the application), but her enthusiasm for loads of other changes being planned made me think it's a low priority. The wider "use non…
-
Not yet. There's a request open to allow people to change their urls (and a wider one to allow people to use urls other than .atlassian.net), but at the moment, all you can do is buy a new Cloud system and move over to it. I should have posted this link before -…
-
You can't really do it. The closest you can get is to buy a new Cloud system, export the old one and import it into the new one. The url will remain <something>.atlassian.net
-
Go to admin -> global permissions and look at the groups that are named for adminstrative access. It's usually easiest to have only one group there, but some places may have several. Then go to admin -> users -> groups and look at each of those groups, removing people as you see fit.
-
I apologise, I have made a mistake. The "administrators" group is not the system administrator's group. It's a bit of a hangover from where Cloud and Server defaults diverged a bit, and it generally means roughly the same as " JIRA administrators". If you want to simplify your groups, then you can safely remove it, but…
-
Nope, your team have JIRA administration rights, not system. You don't get system admin rights on Cloud systems, only Atlassian get that. This doc is for server, so it's not 100% accurate for Cloud, but…
-
A site admin is there to look after all the stuff you've got enabled in Cloud, so not just JIRA. JIRA Administrators is the group for just administrating JIRA (usually overlaps with site admin) Administrators is the group needed to do system administration, so you can ignore it, as it's just "Atlassian support" on Cloud…
-
Look at each project they should not have access to. Read the permission scheme and work out how to change the role memberships so that they do not have access I can't tell you how to do that, I do not know what your permissions and roles are.
-
You will need to review all the projects they should not have access to see how they are getting access to it, and then remove that access. Generally, the group jira-users or jira-software-users has been used to grant access to all projects to anyone who can log in. You'll need to change that model, adding a new group and…
-
You've run into a bug somewhere. It's hard to to tell you more without knowing where it happened, what you were doing and ideally, the rest of the error message.
-
Grant the (fake) group "anyone" permissions to "browse" the project and you'll find everyone can see the issues in that project, without having to log in.
-
50 custom fields is not going to be a problem for JIRA (But it's not going to be nice for your users. Even if it's just one project or even issue type, you're going to find the field names leak out into searches and your users, when faced with 50 fields, will tend to leave as many of them as empty as possible) For the…
-
Ok, so, can you check the status and resolution on your Change Requests? Are there genuinely open and unresolved ones that should be appearing? Can you find one CR that should be appearing on your backlog and show us a screenshot of it in plain JIRA? (e.g. go to https://yourjira/browse/STEST-123 and we'd need the top part…
-
My best guess is that "Change request" is a sub-task type, which won't appear in the backlog view because they're useless in there.
-
Check the board filter in board config - what's the plain text of the JQL for it?
-
You'll need a bit of code to do it (I'd use the script runner), but you could set up conditions that would prevent the use of transitions on the parents until the child issues have been dealt with, and then conditions on the child sub-tasks that prevent their transitions until the "previous" item has been completed. Quite…
-
Have you put your desired text in the right place for the field(s) definitions? One trick to be aware of too - you need to use the "edit" field for create, edit and transition screens - they render differently to simple "view" actions.
-
Try the message field in the Jira toolkit addon (for static text anyway. I think you already know about custom fields for capturing data)