Comments
-
You'll need to rewrite the notfication scheme code in Jira to do this. They're currently quite flat and do simple "on event X, here's who to notify". There's no conditional logic on them, and no support for it. I've seen a request for something like this at https://jira.atlassian.com/jra, but it's not in my bookmarks, so…
-
No, you can only have one production server on a licence. Best thing to do is install it somewhere you can get to on the web, or use a Cloud installation.
-
Another very good reason for not trying to wedge javascript into JIRA. You've got two options really. * Delete the field completely. That will destroy all the data you have for issues though. You need to know the ID of the custom field, so that you can directly paste the "delete" url for it (the delete screen does not…
-
Depends on what you mean by "dated" - it's a bit unclear in the question. On the assumption that you mean "contains a date", then try a JQL search for "reception_date < -30d". That will return all issues where the reception_date field has a date more than 30 days ago. (The -30d makes it dynamic - it always means "today -…
-
Found by, yes if it's on the internet. Accessible, maybe. If you give them accounts, and don't use the "anonymous" option.
-
That's good and bad - looks like a good clean start up of a healthy Jira, but bad because it doesn't give us any leads on what might be wrong. I'd expect database related errors in there if there is a database problem. I'd expect to see stuff about other components if it were something else. I'm afraid it might be as…
-
There should be a "log" or "logs" directory under the location you installed it in. Look for catalina.out or atlassian-jira.log initially.
-
Difficult to tell. What does the log say?
-
I'm good with 180 custom fields in 4.0 and 5.1, although it's always taken a couple of seconds to render (I'm saying there's no change in speed between 4 and 5). How many have you got?
-
Mmm, deleting all your comments kind of make this question into nonsense. Please don't do that.
-
There is no "under". As has been explained to you in other answers, a user has an email address. There is no "add a user under", a user is a single entity with a single email address. If you want to have multiple people get emails when email is sent to a single address, then you need to do it as a mailing list or group.…
-
So give them the same email address. This is not a problem. However, it actually sounds like you want two people to share an email inbox (which is not quite what you've said in either your question or comment). This is nothing to do with Jira, you need to do it on the email server and arrange something with the human…
-
To give the same email address to two users, edit their accounts and set the email address. Your answer is pretty much in the question On the user-management question, could you please re-read the answers you got the last four times you've asked this? The answers are there. (Sorry if that appears rude. I don't intend it to…
-
Versions belong to projects. So your first project has a list of versions to work with and you get to select something. When you create a new project, it won't have any versions to use, until a project admin adds some. So you get "none" until they've been added.
-
That's up to you. Due date is a built-in field, but "implementation target date" is a custom field that your admins have added for some reason. You'll need to look at your process to determine what it means. In fact, a similar rule applies for "due date" - it's up to you to decide what it means in the context of your…
-
I'm not sure I understand the questions, but I think the answers are: 1. No, there are Date fields, and Date/Time, but not just Time. I don't really think there is a lot of use for a time only field - it's not much point saying "10am" - it's pretty much useless without a date type context. Of course, you can always find or…
-
I am sorry, I was not clear there. It is not a setting or configuration element. There are just some places where a user cannot select groups they are not in. It's a hard-coded selection and it only applies in a handful of places.
-
I am afraid not. The permissions to see and use groups is not that granular. There are a few cases where it will limit a user to only be able to use groups that they belong to, but that is about it for now. I hear atlassian are looking at this, but I don't expect it to change soon. is about it.
-
Groups do not belong to spaces, so no. Unless you mean you want to create some sort of functionality which allows you to build lists of users inside a space and then write something else that uses these lists. You can write code that would create groups and then add them to space permissions of course.
-
Ah, excellent. There's always three things when fields go missing - field config, screen and context. Trips me up every time...
-
Have you associated the custom fields with both projects? (Or made them global)
-
Have you associated the custom fields with both projects? (Or made them global)
-
You seem to be saying that you've got 10 (non-Atlassian-admin) users in the system and you're trying to add an 11th. As your licence is for 10, you're getting the right error message. I suspect you've not removed the user you really want to remove fully enough so it's still taking a seat. Have you removed them from ALL the…
-
I'm not sure what you think you've avoided by using groups. Either you can see the users or you cannot. Doesn't matter what group or role you are in.
-
This scenario is *exactly* what roles were implemented for. Stop using groups for most of the access and migrate to roles so you can delegate the whole lot to a project level.
-
I tend to use it when you're messing with the field contexts that are related to single projects mostly.
-
Did you check that the new version of Confluence supports your version of Gliffy? Have you updated the Gliffy add-on to the latest available for your Confluence?
-
Again, you need to read the logs to find out what the problem is. You can not do that on Cloud. So raise an issue with Atlassian Cloud support
-
I'd raise this with Atlassian Cloud support - to find out what it is, we need the logs, and only support has access to them.