Comments
-
Go to Issues -> Search, and run a filter for the issues you want to assign to the user. Then, from the tools menu (near the top right in the results section), use "bulk edit" to edit the issues, setting the assignee. You need to have the right to assign the issues you select, and the global permission for "bulk edit" to be…
-
There's an obvious question - why do you want to do this? Confluence does not need to be re-indexed regularly, pages are indexed automatically. Needing to re-index is indicative of a significant change or a problem with the data. So what have you done to it that makes it seem like it needs doing every morning?
-
Yes. You need to edit your workflow. Look at the transitions (the arrows in the diagram), as these are the things that people click on to make the status change from one to another. Transitions have a set of things that control what they do and who can use them. Look at the "Conditions" for the transtions you want to…
-
I'm afraid not. Create issue permission in a project is all-or-nothing. You could put an impossible validator on your workflows for the top-level issues, but that's an ugly hack and a bit of a pain to implement.
-
No. Confluence's permission system works on either "you can create content, or not" This means if a user has create/edit permission, they can create and update pages in that space. You can use restrictions to stop them editing pages, but the basic access is in the space permissions
-
I'm an engineer. Which, in short, means knowing that ghosts (and a lot of other bullshit) don't exist. The dichotomy for me is that I absolutely love ghost films. I'm typing this while watching "The Babadook" (a bit slow to start but horribly creepy once you get into it) and for All Hallow's Eve weekend, I've lined up a…
-
The training needs to cover all the Atlassian options, so it does not look at the UI a lot. Server Jira/Confluence/Bitbucket/etc is different from Cloud, but the training needs to enable people to use both. Any training you do will be relevant. But if it's based on Server versions, you will need to encourage your attendees…
-
No. You can (and usually should if you have complex stories that different people need to do bits of it separately) split a story up into sub-tasks. But sub-tasks belong to their parent stories. And sprints contain stories. So a sub-task belongs to a story which is dealt with in a sprint, and not the next one. So, if you…
-
No. You can have a permission scheme that says "Project Browse: Role of users". Then you create one project per vendor, and only put the vendor in the role of "user" in their project.
-
Take a step back - your users seem to be confused about workflows, projects and boards. Boards are a view of issues. They do not contain issues or workflows or projects or anything else, they're just a view. Or window on to a data-set. To combine two boards, you need to do two basic things (there's often other things to do…
-
What are you meaning by "linked"? Issue links? If so, what is the starting point? (As Warren says, start by leaving the project out of the query, that will select all projects)
-
Is your sub task type really called just subtask - no space, hyphen or capitalisation?
-
Mmm, the error message seems to be for space to space move, so I think it's the wrong one.
-
No, you can create boards from existing filters or projects, you don't have to create a new project.
-
Ok, and what's the "specific issue type"?
-
You'll need add-ons for this. The ones I'm familiar with allow you to synchronise projects across two (or more) Jira servers, with varying amounts of mapping and interactions. The ones I've used are K15t's Backbone and iDalko's Exalate, which are both good at what they do - there are some others in the marketplace that…
-
The error message says you have the permissions for the database user incorrect. (Or that you're pointing at the wrong database)
-
We need to see the config of the post-function
-
Those look like they are in the same space?
-
You could try converting it, as per Ethan's post, but if it's a client certificate, it's going to be useless to you.
-
Behaviours does not work for Service Desk yet, but I'm told it's on the roadmap for very soon.
-
Software doesn't have that feature of linking to other Jira systems. It would work if you were running Software and Service Desk on the same Jira Core, but it won't work across two installs.
-
Ok, it seems you're quite confused here. If you are trying to run Bitbucket over https, and without a proxy, then Ethan's answer is what you need. However, you've been given a .p12 certificate which is usually a client certificate for connecting to other systems, not for running a server with https. I'd be very surprised…
-
It's being answered on other threads too.
-
You need to explain what "bat" is. To my mind, there's a couple of them living in my roof void, but they are not that interested in Jira. Whatever you mean there though, Gregor's answer is a good one. Use scheduling software such as cron or at to run a script regularly.
-
No. If you don't want people downloading things, then don't put them on a page they can see.
-
6.2.8 was the last one to support Jira 3. Have a look through https://marketplace.atlassian.com/plugins/atlassian-plugin-sdk-tgz/versions But... please upgrade. 3 is old, insecure and totally unsupported. Whoever is making you use it really needs to upgrade and a responsible developer or admin should be telling them that…
-
To amend the Service Desk emails, you would need to unpack Service Desk and hack the templates in there. This is a very bad idea, as it's complex, renders you unsupported and as Gregor says, will be scrubbed by any update. A better way to solve this problem would be to fix your network settings. Jira only has one base url,…
-
Please, step away from the database. It is NOT designed for reporting in any shape, and there is almost certainly a much better way to do what you want. Could you explain why you are looking at it? And who gave you the terrible idea of using SQL to do it? (If you must, then start with changegroup - it has an issue column…
-
Ok, that's very clear - your database is not configured correctly, and Jira cannot write to it. Even if corrected, the data might be damaged. You will need to fix this database error and retry.