Comments
-
What does the log file say the problem is? <confluence home>/logs/atlassian-confluence.log
-
No, there should be no problem doing it. Import the libraries you need into your add-on or script and run the SOAP calls as needed.
-
Yeah, the "workaround" in Portfolio is not ideal, it just automates some stuff which is not a real fix for the lack of shared components.
-
No, that's not possible I'm afraid. I would look for a better way to identify issues than a list of keys. For example, are you watching all of these (and not others in the project)? Or could you put a label on each one? What do they have in common?
-
You can do this without add-ons, but it means moving the edit into the workflow. Take the field off the issue edit screen, as mentioned above. This allows you to create an issue with it, but then no-one can change it. Add transitions to the workflow, such that: * They go back to the current status * They have "transition…
-
There are somewhere between 12 and 26 highly inefficient joins you would need to make in to replicate that JQL in SQL. Probably towards the higher end if I remember the Software data correctly. Please, don't. The Jira database is not intended for reporting like this and SQL is the worst possible way to report on Jira data.…
-
You will need to configure your email client and/or server to send the emails to Jira with proper mime attachments, not convert them to windows mail .dat files.
-
You'll need to make copies of the query and add more clauses to it to break it down. For example: * Issuetype = bug (100,000 results) Could lead to things like * Issuetype = bug and category = billable * Issuetype = bug and assignee in (Alice, Bob, Charlie) and so-on. There are also some gadgets and reports you could use…
-
Absolutely not. There are significant parts of <jira-home> that will not work on shared storage. You should only move the attachments directory.
-
You'll need to explain what way you want to do it (Tomcat? Proxy? Which proxy if so?), and what docs you have tried to follow?
-
No, the dates get moved into the date section.
-
Could you try sending a test mail, with the logging enabled (from the mail server setup screen). That should give you more of the error than "connection timed out"
-
Go into the project settings and find the "fields" area - look for the "field configuration", you will find that the "time tracking" field has been set as mandatory. Turn that off.
-
Look at the board configuration - the main page has the board filter and a sub-filter on it. An issue needs to match both of these. The board filter is "show these issues" (e.g. "Project = X") and the sub-filter is for "these issues are done" (usually boils down to "a fix version is not set"). A Kanban board hides "done"…
-
All releases on the standard download page can be described as "stable". See https://community.atlassian.com/t5/Jira-questions/which-version-of-jira-is-stable-in-market-right-now/qaq-p/934123 for the previous recent discussion on it.
-
No, the error is about a corrupted file in your cache from the look of it. Could you tell us what the on-screen error is, not the one you get from the js console? And ideally the error in the Jira logs that should be seen at the same time?
-
The "cross project release" works by creating separate versions with the same name - one version per project. That's what you're seeing on the gadget. There's no way to see them as one (without code), because they're separate.
-
You need to be in the diagram view of the workflow to work with the "all" transitions. You need to be editing the workflow to get to the transition settings.
-
Should be in the ... menu to the top right of the board. Unless the board is from a "Next Gen" project, where you're a bit stuck as they aren't really configurable enough yet.
-
Quick filters are not for selecting issues for the board, they are for drilling down into a board by letting you further filter the issues after the board filter gets them. To get an issue on the board, it has to match the board filter - go to board -> config and the main page, that has the filter definition on it, and…
-
I'd create a new board, with a filter that pulls out the issues you want to see on it. The question becomes how you identify these issues - is it as simple as "they have a project manager in a field"? Or maybe you label them, or possibly an issue type with the assignee being the PM?
-
Jira does not have a concept of sub-projects. Most of the advice you'll find will start talking about using "components" to distinguish between different parts of a project.
-
Ok, that's good, it suggests it took a backup before overwriting anything on upgrade. You could try installing an empty 7.12.1 and importing that .zip into it!
-
Ok, not quite. The "project category" on the project is a category field that is built in, it's not a custom field. You can actually already use the "project category" in searches - it's shortened to "category" so you can use the JQL "category = 'Crowdfunding'" That doesn't come out on issues themselves, but in cases where…
-
There is no roll-back, and I suspect your "uninstall" may have removed the service completely, so there's no install for the next run to upgrade! You'll need to work out exactly what it has done - do you have the "jira home" directory ok? (Don't panic if not, but if you don't have it, it's going to be harder). The basic…
-
Everywhere, absolutely everywhere I've been, multiple assignee means "I thought the other one was working on it". In real life it does not work. There is no harm in having an extra field for other involved people or groups, but the assignee means "this single person is the one currently responsible" (even if it's just…
-
Nope, if it's not in the compatibility guide, it is not supported. It does tend to work ok, but you can't rely on it, and if you have any problems, the response will be "move to a supported database"
-
I apologise for not being able to answer in Dutch. You can have up to 100 users, yes. You can have * 50 with access to Core and Software (boards etc) * Another 50 with access to just Core This is because the 50 licences you have for Software allow those users Software and Core. The Core licences only give access to Core,…
-
I don't think that's unreasonable. But I would question why you're being asked to shut down a project that has work that needs doing in it. Surely those should go on in that project until they are fixed? I don't think there's anything wrong with another project absorbing outstanding bugs etc, but I would question why…
-
The issue view takes the list of your fields and re-arranges them into a set of panels. Dates and times get pulled out into a date panel, people and groups go into a panel, the system fields go into another, estimate and work-log another. Description, links and subtasks all get their own panels. Once it's pulled those out,…