Comments
-
For new features/requests, have a look at https://jira.atlassian.com I'm not sure this is one that would work too well though - a lot of Jira sites don't want that done automatically, because it's not right for them...
-
Sorry, hit enter too quickly!So, what you need to do is look at the notification scheme for the project. If that is too noisy, get the admins to change it. Bear in mind that most of the recipients of emails are variable but not directly controlled by you - assignee, reporter, members of groups or roles, etc. Watcher is…
-
:-) Yes, that's exactly what autowatch does.Being a watcher is not the only way to get emails, but it all depends on the notification scheme. The default scheme says "All events notify the reporter, assignee and all watchers", but you can change that on an event basis, so you can have rules like "issue closed = reporter…
-
No, you're reading the middle paragraph of Ignacio's answer.Please read the middle paragraph of *my* answer.After that, you then need to understand that autowatch does not toggle any emails. It makes you a watcher. What your notifications do after that are another story.
-
Please read the middle paragraph of my answer.
-
Autowatch means "add me as a watcher when I comment on, or update, an issue". It only applies at the time at which you make changes. Turning it off means that you will not be added to any more issues you comment on or update, but it has no effect on what you did in the past (because there's no way of knowing if you clicked…
-
There's no way to do this natively - if a user can create an issue in a project, they can create any type. You can do a slightly ugly trick of making some issue types fail validation, but that irritates users because they put their data in only to be told they're going to lose it all. Your best bet is an add-on that can…
-
I am so looking forward to the new answers replacement not doing "share with random person who has high points because I think my question is more important than everyone elses"
-
>So is there any possible issues which could occur while updating the resolution directly in the database WHILE Jira is running? You could destroy a chunk of the project. I've only seen it happen a couple of times, but direct modification of the issue table while Jira is running can lead to a LOT of serious damage…
-
You'll need some code in order to do that - a listener that can pick up issue-created and issue-updated on subtasks, read the component field and check the value of the parent, adding any components as required, and removing any that are removed from the sub-task after checking all the other subtasks don't have it. Note…
-
Er, see the document you've linked to in the question. If by "sample" you mean "trial" or "example", then yes, you can get evaluation licences that allow you to try out the software for free. These simply expire after a set time (but still allow enough access to allow you to put in a full licence later)
-
Your options are very limited here. To avoid loss of history and data, you're basically down to two options - What Henning said - even the Jira CLI and Jelly can't delete the comments, the script runner pretty much is the only approach - As you said, hack the database. You will need to stop Jira, get a backup, remove lines…
-
Start with https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions The basic idea is to work out a way to differentiate between your users and then set up permissions so that people who should see A and not B only have access to A. One difficulty you'll find is that Atlassian defaults are unsuitable for…
-
No, you will need to licence them. You should talk to the vendors about "free" licences if you are a charity or open-source supplier, as some vendors follow Atlassian's model of providing free licences to certain types of organisations. But I can't tell you if these vendors follow that model or if they've got their own…
-
There is the option C. Faysal gave as well. Everything else requires code, whether that's injecting javascript or hacking core code. I don't think this is something that's possible in a plugin (although a plugin might be one way to get your javascript in)
-
That's a function of the operating system and security layers, not the application. When it comes to compliance with assorted arbitrary rule sets, see https://www.atlassian.com/trust/faq on the subject.
-
The icons on the selection list are generated from a properties file - you need to edit that and restart Jira. Or you can just use a full url to the images.
-
And, if you move a page and someone lands on it because they have an old url, Confluence does the right thing and says "this page was moved to <new location>" That more than answers the "basic requirement" because your obsolete urls still get you to the right page
-
Yes. A board filter can say things like "Project in (X, Y, Z)", and your suggestion of "one project per website" is a very sensible approach.
-
It doesn't really. There are new APIs etc to deal with in the code, but the way the licences work is broadly unchanged. The number of licences you need for an add-on remains as "it has to match the licence you hold for JIRA" There is a slight complexity with the new applications though - if you've got JIRA + Software +…
-
Um, http://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens ?
-
The wait command is case sensitive, you'll need to get it spot on. If 500 fails, then you may have too little resources to get JIRA running on the machine - you could try 1000, but I'd be looking at the CPU and memory on the machine too - is it really up to spec?
-
(Also, I'd like to see if it all runs ok if you run without the plugin)
-
Oh, that could make it worse - stick with 1.7, the usual cause of this error is using an older unsupported version of Java.So, it's not the easy one, we need to look in more detail. The error is occurring when it is trying to load the "roadmap" addon, so that's the first thing to check. What version have you installed and…
-
What version of JAVA are you using for JIRA?
-
Post-functions are too late. Try Conditions on the trnasitions - only group A can do X, only group B can do Y and so on
-
No. The workflow used by an issue is completely determined by its project and issue type. You can do things inside workflows with groups (e.g. only allow transition X to be done by group Y), but the workflow is locked to issue type.
-
Essentially, no, to all three. 1. This is mostly because there's no real use for the separation, it generally just confuses users, and on a technical level, every "edit" is actually a new page. 2. Again, this has been found to confuse users 3. Part of the point of Confluence is that you can see the history
-
The Epic Name field is locked to prevent misconfiguration. However, I'm not sure how you've managed to do it, but it is already mis-configured in two ways. The first one is that you have a duplicate name - that first field should not exist. The second field there should have "Epic" underneath the "context" column. I think…
-
What does the log file say?