Comments
-
No, but you can add as many boards as you want. So if you added a Scrum board, and then deleted the Kanban one, it would have the same effect!
-
>I know I can use an inclusion library for Confluence chunks/pages I would still do that - it means you only have to save one file in one place. Davin's trick then solves the other part of your problem. Although, if you can't do that, I'd be looking for a script that can monitor a remote or shared folder and either drag it…
-
The issue view screen is a screen inside Jira Core, used for viewing all the issue detail. The Kanban board is a view of a set of issues, and the fields it uses are selected in the board configuration. Have a look at the board settings.
-
Create (or find) a workflow scheme that maps the workflows you want to use repeatedly. Go to each project you want to share it with, go to project admin, find the workflow section and change the scheme to the one you have chosen. It may ask you to migrate if the schemes make status different, but it walks you through it.
-
There are other add-ons in the market place (if you look for estimate or estimated date, you'll find a few), but the ones I've used that do things like this are Portfolio (Atlassian), Tempo planner (Tempo) and Cycle Control (Botron). They all take different approaches, but they can all deliver you dates one way or another.…
-
Best case - you lose some of your writes. Worst case, you lose entire issues or even a project. Never write to an active Jira database. It's pretty much guaranteed to go wrong. Whomever decided this was even a remotely sane approach is wrong. Use the API to make updates.
-
Absolutely not. The board deselects them because of the sub-filter, that's what it's for. Remember - boards are a VIEW, not a container. The issues have not moved, just had data added. They'll show in reports, projects, searches, filters and you can still change them, permissions and workflow allowing.
-
Ok, so you're not updating the counters? Can you confirm you are making these changes when Jira is completely offline? And ideally after you've taken a database backup?
-
The usual culprit is rogue emails, ones that Jira is getting part way through creating, then failing, but not deleting them. Do you have any mail handlers configured? Also, is it one project, several or all?
-
What other SQL are you running as part of this update? I ask because you might do this safely, but your question doesn't mention the other things you must do if you're going to mess with the numbers, so I'm a bit paranoid (having had to rescue so many systems where someone touched the database)
-
The project will stop allowing issue creation, you might not be able to search it, and you'll get errors displaying project reports and boards.
-
Yes, corruption of your database is a significant risk, although the worst it will do is break the project where you do this. I assume this is a one-off change to get you started though? Not something you do when Jira is running?
-
The Script Runner add-on would let you do that (and loads more), and I think the Automation add-on does it too. I think there are a couple of add-ons that can do something similar in a more locked-down way.
-
It's not the permission to share that is the problem, it is not being able to get to it because the page has vanished. This is something your browser is doing. Is your browser a supported one for this version of Jira? Could you try a different browser, or the current one with "safe mode" enabled? (All plugins disabled)
-
That message means your browser can't reach Jira, or that it can but Jira is not listening. Check your network and check what Jira is saying it is doing in the log file.
-
It does, but you can change the projects to use a single shared workflow, or set of workflows, or have groups of them. (E.g. one set of workflows for developer projects, another for support, another for non-IT projects etc)
-
There's a good Atlassian-focussed getting-started article on this at https://www.atlassian.com/blog/jira-service-desk/jira-service-desk-approaches-itsm
-
No, and it's complex to implement correctly. One thing I've looked at in the past is the access logs - it's easy to scan those for <base url>/browse/xxx-nnn, and you could, in theory, do much the same by injecting tracking javascript into the issue view screen. But that tends to miss a LOT of usage. The manager who asked…
-
I would attach the spreadsheet to one page only, then either: Point your macros to that single attachment If your tables are all the same, put them on the attachment page and then use "include" to draw that page inside other pages.
-
I seem to remember the integration between Service Desk and Confluence improves for Jira 7 with articles being directly suggested to agents and the ability to email them straight to customers.
-
It's the same answer. JSD is installed into Jira Core as an application for it, and relies on Core to provide the projects it works on top of. So problems in Service Desk will manifest in Core.
-
There should be a pencil icon next to the licence key to put it into edit mode.
-
It restores everything
-
There's no function for it in Jira. It's because Jira is an issue tracker, not a documentation tool. 90% of people who are tracking an issue care nothing for the history of it, just what needs doing now or next. Of the 10% who do care, 90% of them will only be looking for a very specific single change, and 90% of the rest…
-
@Bridget- I may have missed out because Hipchat doesn't tell you when you're added to a room. I've been asked to sign up to the Amsterdam one, but didn't see the request for a week, so I might have missed it.
-
There is no way to do this with Jira. In Jira, a custom field is a single entity. It exists once for each issue, although some custom fields accept multiple entries. As an example, imagine you have two fields: * Colour:* Has a list of options: Red, Orange, Yellow, Green, Blue, Indigo, Violet * Can only hold one value *…
-
I'm afraid mass-updates are not a native function. You'll need something like Script Runner to make bulk permission changes. You have started on the right path to fix "limit user to a few projects", but I'm afraid Jira's defaults conspire against you. You need to go over every permission scheme, checking who matches the…
-
Create/Edit in both spaces - you need to be able to edit the page you want to move, and create pages in the space you're going to move it to.
-
Can you check the context setting in <jira install>/conf/server.xml ? The upgrade may have stripped out the setting if you've used it.
-
Exporting does not touch the issues - that would be a nightmare!