Comments
-
Filter results shows a list of issues (truncated if the results are large, but the watched issues gadget does a similar truncation) The option you are asking for here is counter-intuitive at best, and quite hard to code for too. You'd need to be asking the dashboard if there are other gadgets that might be showing issues…
-
No, the gadget does what it is supposed to, and what people expect it to - shows you the issues you are a watcher on. It would be counter-intuitive to have it start dropping issues out because they might be on another gadget (that this gadget has no information about) You should replace it with a "filter results" gadget…
-
The basic email handler built into JIRA will do that. What do you need that https://confluence.atlassian.com/display/JIRA/Creating+Issues+and+Comments+from+Email does not do? (although I'll probably end up recommedning JEMH as usual)
-
Er, hang on, you're getting the setup screen there. So, it's working.
-
There should be more log than that. But, can you have a look at system load - how much memory and cpu are in use? What are you allocating to the JVM when it starts up?
-
Well, actually, yes, a broken file system will stop it completing startup. This looks like it got part way through starting, failed and then when you restarted failed again. I would * Stop Jira, leaving it for several seconds and checking with a process viewer that Jira is no longer running at all ("ps -ef | grep java" for…
-
There should be more than that. Even when it fails to start, there should be more. If it really is just stopping dead at that point, then you probaby need to check the load on the server - is it thrashing memory and/or CPU
-
It might not look like errors. What does the log say from "You can now access JIRA" onwards?
-
You need to keep reading the log. It should contain reasons why the service has not started fully.
-
I doubt that they are. They might look numeric because you've set them up with options like "1, 2, 3, 5, 8, 13, wtc", but you'll find that they are either bounded type fields, or of types provided by a plugin like I mention.I apologise. I should have been more clear about what I meant by "type". That's the type of field,…
-
The list of fields for the 2d gadget and some others is determined by whether a field is a bounded list or not (effectively a fixed list of possible values, rather than an open ended arbitrary data set) All the types of select list are bounded lists, but obviously, text fields, number fields and dates cannot be. I suspect…
-
The basic trick behind it is to create a project where the permissions say "browse = reporter browse only" - that's a special flag you have to enable in a config file.
-
You can't create issues outside a project. With a bit of tinkering, you can create a project that will act as a private to-do list for anyone who needs it though.
-
The Jira Agile plugin implements Scrum and Kanban boards which have exactly this facility.
-
Hmm. I'm not sure how it works in servicedesk. In plain JIRA, the column "rolelevel" on Jiraaction covers it.
-
If you've inherited a really old Jira dataset (as in 2.1 or lower, although you don't want to rely on my memory for the exact versions), you might find Jiraaction has history data for issues updated while it was on that version. I don't know if later versions actively copy or move the history data to changegroup and…
-
Older Jira systems used to store other stuff in there, so you might find historical data from version 2 if your system goes back that far. I don't think the more recent versions of Jira store anything other than comments in it, but I'm not 100% sure. If you've found things other than comments in there, be interesting to…
-
You can read it straight off their activity stream in their profile. Or, if you insist on SQL, look in "jiraaction". You'll probably want to join it to jiraissue to find out which issues the comments were made on.
-
JIRA ships with a handful of standard workflows it uses when you create new projects. You can add workflows from the marketplace You can define your own workflows I'm a little uncertain on what you mean by "manage predefined workflows" because of the stuff I've just mentioned above.
-
You've installed something on your machine to provide a service. I'm not sure how you'd expect that to be running if you turn it off.
-
Not really. In the broadest sense, a "server" is simply a computer that is running services. Modern operating systems tend to run loads of things as services, even if they're only accessible on the current machine. Confluence is another service that you've added - it doesn't make the computer a "server" any more or less…
-
It's very unlikely that no event is being fired at all when the transition is performed - I don't think you can remove "fire event" from the post-functions at all. I'd check that it is defintely set to fire "generic event" and then see if anything goes into the mail queue at all. This could be hard to spot, as the mails…
-
Yes, assuming that's the one your transition is firing.
-
>When it is reassigned back tot he reporter I think that might be part of the problem. The "issue assigned" event is *only* fired by the "assign issue" action. If your users are changing assignee as part of a workflow transition, then there is no "issue assigned" event, you on;y get the event that the transition actually…
-
As we're end-users like yourself, anything we tell you can't really be taken as auditable confirmation. Raise this with Atlassian support at https://support.atlassian.com and you will get an authoritative answer.
-
Why don't you want to use the one method that is explicitly designed for handling this case?
-
Correct. Jira's mandatory fields are mandatory throughout the lifecycle of an issue. One of the very earliest plugins I've ever seen was written to provide a "validator" that fixes this problem. You put a validator on a transition to check that certain things are done before allowing the transition to run. You can probably…
-
You can use simple numeric comparisons on dates and times, so you can easily do things like "due date > 30/01/2016" to say "due date is after the 30th of January 2016" You can use dynamic dates too - "due date > -7d" means "due date is set to after 7 days ago when this query is executed" And there are functions, so "due…
-
It's covered by https://confluence.atlassian.com/display/JIRA/Modifying+Multiple+('Bulk')+Issues - bit of a long doc, so yell if you get stuck part way through.
-
You may need to make sure you have the rights to use bulk-edit. That's under "global permissions" in the admin section. If you have that right, then bulk-edit can be found if you go to a filter and look in the tools/cog menu