Comments
-
I'm afraid I don't know the database well enough. I'd start with shutting down Confluence and going through the "clean out plugins" routine, but after that, you'll need to drop all the data that the plugin has inserted, and I don't know where that data is. I'd be strongly tempted to do the wipe of the test instance, but I…
-
It's not yet a year old, so it was a bit more recent. Thing is, they shouldn't have trialled it in a production system. That's the awful way to do a trial - it should have been done in a test system which you can tear down and rebuild from your production data. To continue the trial, you've got two basic options - strip…
-
That sounds like you trialled it on an older version, removed it, upgraded Confluence then tried to get another trial. Confluence won't have installed an old version that was incompatible with the current install, so that's the only way I can imagine you can get into this state. You could try removing the plugin…
-
Code, and quite a lot of it. Atlassian are not going to put the fields side-by-side any time soon. That means if you want to do it, you have to either change their code in the core of JIRA, or come up with javascript hacks to re-arrange the screen (usually ugly, and often unreliable) On the other question - yes, remove…
-
Ok. Well, the "stuff that was recently updated by user" will stay, but it won't include content from pages that your restricted user cannot see. The ability to look at other users profile is not globally restrictable (as far as I know). Atlassian are trying to make Confluence "social", and I don't think it's possible to…
-
Yup - you needed to let them "log in" as well as the rest. You can't restrict access to the dashboard itself, but the dashboard will only display stuff about spaces that the user has the rights to see. If the "public" space has "anonymous" access, but no other spaces do, then the user will only see data related to that one…
-
There's several layers of access. In no particular order, you need to think about Space permissions (Your setup is fine there) Page restrictions - either on the current page (again, you've got this covered fine), and also on all the pages *above* it in the hierarchy because restrictions cascade to child pages…
-
Your network is not configured to allow JIRA to talk to itself externally. This could be routing or firewalls blocking it, but the usual culprit is that you're using SSL and you have not given the keys to JIRA to enable it to go out and back to itself. This isn't the reality of the setup, but it helps to debug it - think…
-
I take it you are looking in the list provided in "find new add-ons" in JIRA? That has a safety feature in it - it won't display add-ons that don't have a version valid for your system. Have a look at https://marketplace.atlassian.com - is the add-on listed there? Click on the versions tab to see what versions are…
-
Ah, I didn't know that. Sorry.
-
Eh? You don't need anyone to provide an add-on, you can just install it from the add-on manager in the UI.
-
You should be able to re-install the add-on (even if you leave it unlicensed, but active), delete all the fields from the custom field list, and then remove the add-on again. Unfortunately, if you've "deleted from the database", you might have damaged it too much for this to be possible - you'll need to undo those…
-
Absolutely not. Your production key is for production and should never be shared. However, your licence entitles you to a developer key, which you can use for dev, test and failover purposes. On multiple servers. On any valid version of the software. As long as you don't treat these system as live. Log into your…
-
Absolutely not. Your production key is for production and should never be shared. However, your licence entitles you to a developer key, which you can use for dev, test and failover purposes. On multiple servers. On any valid version of the software. As long as you don't treat these system as live. Log into your…
-
So you did not compile it? Why did you say you had? Have you checked the permissions on the file? Can you tell us *exactly* what you have done, step by step, clearly, with paths and file names and what you're putting in fields?
-
Eh? Compile it? The whole point of the script runner is that the code is run as it is. What part of the docs said you should compile it?
-
That usually means it can't read the file you've given it. Check location, permissions etc.
-
You can't just cast a string to a date - the lines using "new simpleDateFormat" is completely wrong because myDueDate should be a date and not a string, and the following line is worse because it casts a string to an object rather than a date. Try losing the cast in the second line, and making mydueDate a date instead of a…
-
You'll want to create a custom field to cover that. Or use labels maybe.
-
They're all the same. You can use the project "category" to help group them together, and if you give them sensible names, it helps when searching them. I'm not sure how you'd "value" a project though.
-
Relying on email? Rubbish, most of us turn most of the email off, and sit on the HipChat notifications.
-
JIRA does support "send email to one set of people and not another" in the notification schemes - the best option is to set it up for any particular event to be sent to the right people. I usually recommend going over each event and thinking about who needs to get it individually - the default of reporter, assignee and…
-
You need to go over the notification schemes with your administrators to make them more fit for your needs. Remember that JIRA is about sharing, not getting totally different sets of information because you don't feel like seeing what your co-workers do - the schemes mean people get consistent behaviour and know that…
-
You can't do that with javascript alone. Javascript runs on the browser, not the server. To make this work, your javascript *must* write something back into the page to save the information that something has been hidden, so that the next time the page is rendered for another user, the javascript can read it and hide it.…
-
Ugh, mind the caps-lock key Anyway 1. Make component mandatory in the field configuration 2. Create a filter that looks for all issues in the project(s) you're interested in and save it 3. Create a "dashboard" (consider using the default system one so everyone gets it). Add a "2 dimensional filter" gadget, selecting…
-
You have not mapped the values correctly when setting up the import.
-
Resolutions are global, they don't have contexts or schemes like custom fields do. It's a single list, available to all issues irrespective of issue type or any other data. However, you can do it with a bit of work. It is NOT directly related to issue type though, it's done via workflow. In JIRA, you can associate…
-
Most of the "global" stuff has been absorbed into the board configs now.
-
That's part of a view of a standard issue. I'm not sure what the problem is - it looks like this issue has some sub-tasks and some links. You've not shown us the header of the issue where you'd see the details for the (not sub-task) issue.
-
You do have three different ways to do this - where you can, you should try to use the same method as much as possible - keep the complexity in one place! Field configurations - will let you show/hide the field on a project by project basis Field contexts - much the same, except more global - this affects simple searching…