Comments
-
Mmm. * It's a 3 year old question. (I was talking with Atlassian 48 hours ago about deprecating old content on Answers, we're working on that sort of thing) * OnDemand doesn't exist any more * It's still valid for Server.
-
Yes. The footer tells you the version.
-
That means you've either given the wrong connection details, your network is not allowing the connection, or your email server is not listening for the connection.
-
That is too vague a question to answer. What do you mean by "setup with office 365"? What are you trying to do and what are you expecting to happen?
-
You're going to need to give us more than that (although I can start with "you will not get access to the Cloud database, you have to use REST or the UI")
-
1. No. The updated date tells you when the last change to the issue was. You're changing the project, so it's correct. You'll need to write your own "move" process to retain it, or botch the existing code so it becomes inaccurate. I'm not even sure it's possible - I have a horrible feeling that it's a derived field, so it…
-
Simple answer - 5.0 is better than 4.x There are some minor reasons for staying on a lower Jira, but I can't judge whether they apply to you because I don't know your users, setup or actual usage. Generally, I'd go with testing 5.x with one of your power users and if they don't stumble into any show-stoppers, go for it.
-
I'd recommend that you don't. Every system I've seen with defaulted text like this is littered with tens of thousands of identical (and hence useless) descriptions filled with just the default.
-
Status are shared objects, not per-workflow. Your four workflows share them, so when you edit it, the others are affected. Have a look in Admin -> Issues -> Status to see the list.
-
What do you mean by "schema change"? If you mean you changed schemes, then most of the time, all you do is re-apply the old one
-
Er, we need more than that if you want us to help you. What's the error message, what have you done, versions, what does the log say?
-
Ketchup?
-
When looking at versions, always check the "supported platforms" page. For the latest version of Confluence, it's https://confluence.atlassian.com/display/DOC/Supported+PlatformsAs I was scribbling this answer, that doc was for Confluence 5.7 and said "Use Java 7, latest release, and PostGreSQL 9.2 or 9.3". So I'd strongly…
-
I'd tend to agree with Mike on this - I've had strings of problems with using MS-SQL for all sorts of applications, even Microsoft ones. Not just performance, although I've seen bottlenecks and intermittent slowdowns vanish by simply swapping to one of the other three supported databases. It's going to take you some time…
-
You don't - you'd have go through every scheme and update every single one, or change all the projects. Two options * Bin the email entirely - see https://confluence.atlassian.com/jirakb/how-to-prepare-a-development-server-s-mail-configuration-297669416.html to see how to shut it off completely * Put a mail proxy server in…
-
And for improvements and new features, jira.atlassian.com is the place to raise them publically
-
Ah, I've seen that message when a script is going wrong on create (last week actually). That was down to my dreadful script-runner code, but the log file was clearly pointing at my script. As you have nothing in the log, it shouldn't be that, but I wanted to mention it just in case it could be. Could you list out the…
-
Start with the error message - what does that say?
-
Ah, no. Close, but not quite. Watcher is a system field (it's always there, unless you turn it off). It lets users simply add themselves to the issue so that they get updates about it, but they don't need to comment or update the issue in any way, it's purely "I have an interest". I use it a lot on Atlassian's Jira to keep…
-
I meant that as I clicked "comment", I had an idea on how to find the comments - the "participants" field lists all users who commented on an issue, so if you search it for the user you want ot remove, you'll get a list of issues where they commented, so you can delete them.
-
It's in the permission scheme(s). You'll need to check every active permission scheme. Personally, if I were you, I'd just add "can delete anyone's comments" for Jira administrators only (there's no audit logs on deleted comments), that way none of your other users will click the wrong thing :-)
-
Ooh, well, you can delete comments - just a matter of setting permissions to allow "delete anyone's comments" However, no, I can't think of a quick easy way to identify them. Edit - yes, click "comment" and then have an idea! Use the Jira Toolkit, it has a "participants" field - add one of those fields if you haven't…
-
No, you can't. The tool is built in a way to prevent you destroying information, and that includes user activity (that's actually the single most important audit point in many fields that Jira gets used in). The solution is to accept you can't destroy user information without major surgery. (And a visit from the regulators…
-
To "close" a question, mark one of the answers as correct - look for the tick to the left of them
-
Ah, bother, a condition for "user is project lead" is not part of the core of Jira and you may need to install a plugin to do it. Sorry, I may have mislead you there. I usually end up with "people with project admin rights can do X", and a permission scheme that includes "project lead has project admin rights", which does…
-
The workflow is up to you - although Jira ships with default ones, you can change them. The workflows have conditions on them which are controlling who can and can not do things. For example, on the default workflow, the "resolve" transition has one that says "User must have resolve issues permission" There is some logic…
-
Joe has pretty much said a lot of what I would already, so I won't repeat it. I think you'll need to change code in the core of Jira. The reason is that the framework that draws the screen is making the decision whether or not to render the field, way before you look at the templates. I imagine an internal dialogue like *…
-
The issue key in an import needs to be a reference to an existing issue key - the import will be using it as an update, or a place for sub-tasks. You don't get to set an issue key in the import - if your project is on ABC-123 and you import 100 issues, they will be ABC-124, ABC-125... ABC-223
-
The usual culprit is that your account does not have the permission to see the 11 issues - blocked by the permissions scheme or security scheme. If that's not it, then the next suspect is a broken index. (Although it might be worth running a re-index first, as it's an easy one to rule out - to deal with the permissions,…
-
That's not at all strange. Cloud has never had that option, you don't need licence details because you're on Cloud. I didn't know that trick about entering the url for Cloud, sneaky.