Comments
-
In the space permissions, grant "confluence-users" (or your login group if you have another one) view access to the space. If you want the world to see it, grant anonymous access as well.
-
You're probably alright then as you're giving it plenty of time. People reporting via SQL and getting the wrong answer was the first thing that made me start looking into JIRA database usage, and very quickly lead me to "the database is always the worst option". There are times when it's the only option, but it's always…
-
A user can select their own gadgets on their own dashboard, or choose to look at other people's dashboards. If they don't do either of those, then no, they use the system dashboard, and there are no (built in) gadgets that look at a users' group and change their display.
-
What method did you use to "migrate the project"?
-
The bi-directional nature of links is absolutely not redundant. Consider them in a simple sentence. Let's say I've got issues ABC-123 and DEF-456. With non-directional links, you'd only be able to say "ABC-123 is linked by 'Block' to DEF-456". You cannot tell from that sentence whether ABC-123 is blocked by DEF-456 or…
-
The key of your licence is linked via the server ID, but you can change the server ID on your licence, and importing the data from the old server on to the new one will not break anything (it may ask for a new licence before becoming fully functional, but you can work with evaluation licences until you've got the new key)
-
What type of field is "calculated risk"? The search depends on the type of field, as different fields have different ways to search. A "greater than" search is almost always nonsense for a text type field, and probably should be searched as "alphabetically higher" instead. Equally, a fuzzy text search on a date is useless,…
-
Yes, although I did it on a Linux box, I would not expect it to be any different on Solaris. I was having problems with networks allowing Synchrony to work, and we'd turned off the collaborative editing while that got fixed. We upgraded with no problems, with it disabled, and then added it back later when we'd fixed the…
-
See https://confluence.atlassian.com/adminjiraserver071/customizing-email-content-802592932.html for how to amend the emails
-
I'm sorry, I can't work out what that means. The main problem I have is understanding what "sprint greather than" mean? For example you say: Stories with the Sprint greather than the parent Epics Does that mean * Stories whose estimates add up to a number larger than the estimate on their parent Epic * Stories whose…
-
That method may not give you the right answer if a change was recent.
-
You need two field configurations - the one you currently have, which shows it, and a second one that hides affects version/s Then you need one field configuration scheme which tells the project to use the one with the "show" for bugs, and the "hide" scheme for all the other issue types.
-
It's almost certain that one of your administrators has renamed or removed a field called "Datacenter" Go to the filter and edit it, removing the clause with the field in it. (Or contact your admins and find out why they removed it, and maybe get them to put it back)
-
If you bought it for Server, then sometimes, you need to wait a couple of minutes for the licence to appear. If you bought it for Cloud, you don't get a licence, you just go to your Cloud system and it will be there, after a while (Atlassian say it can take a while, the longest I've waited is about 40 minutes)
-
The only ways to block deletion are: * Not having the permission in the project * Workflow properties on all the status removing the permission * Add-ons blocking it What does the permission helper say?
-
Ok, that's good. A Scrum (and actually Kanban too) are usually views onto issues, not issue containers. If you're using a non-simplified workflow then you've not done any damage to any of your data. (If you're on simplified then you might have, but JIRA would have asked you to confirm that you wanted to change the status…
-
Still that Atlassian JIRA install, but the message is the same - Atlassian have no plans to make it more flexible, so you're into hacking it. (And it's going to change a lot on Cloud)
-
Generally, running SQL against a JIRA database is the worst way to do any form of reporting. It is not designed to be reported on. Of course, the application has no way to get to the database either, as you shouldn't be doing it. And, never, never, never, write to a JIRA database. To run your SQL, you will need a database…
-
I think so, although I'm not sure if the permissions will work the way they do in a post-function.
-
The errors you have posted here are shut-down errors. You need to look at the errors that occur on startup, and then when you try to hit the url and get the access problem report.
-
I can't think of one off the top of my head.
-
It would be better to use the standard upgrade route, not export/import. You'll want to follow https://confluence.atlassian.com/migration/jira-7/server_jira_upgrade and in the bit that says upgrade, run the installer as usual and choose the "upgrade" option rather than install.
-
Not quite. You'd have Task 1. Task 2 would be a sub-task of 1. You would not be able to close 1 until 2 has reached a certain state.
-
My guess is that you are on Cloud? You cannot change the url of a Cloud service. The best you can do is buy a new one with the new base url, export the old one and import it into the empty new one. Bear in mind that the domains are still limited to atlassian.net ones.
-
Use one of the synchronisation add-ons to duplicate the projects you want to share, then you can build dashboards locally.
-
Correct, you can't use it on Cloud. You'd have to contact the vendor to see if they have any plans to build a Cloud version.
-
JIRA and Confluence are two separate systems. You will need to install Confluence as a separate thing to JIRA. (Technically, you could run them in the same Tomcat server. But never do that - it *will* break, in bad ways) My dev setup has JIRA and Confluence running as two independent installations, but on the same physical…
-
You're already using it, it's a key part of the AO functionality. See https://developer.atlassian.com/docs/atlassian-platform-common-components/active-objects/developing-your-plugin-with-active-objects/the-active-objects-library/creating-an-entitymanager
-
Is your add-on loaded ok and enabled? What does the atlassian-plugin.xml say the field type should show as?
-
No. JIRA Service Desk is designed and intended to give customers a simplified request view, not expose the behind-the-helpdesk view to them. If you want people to see the issues behind them, you need to give them full JIRA accounts, or grant anonymous access to the JIRA projects.