Comments
-
You're going in the right direction - using emails -> file, but I don't understand why you're leaving the subdirectory blank - the wole point of it being there is that's what Jira is going to scan for mail...
-
Maybe
-
Ok, could you have a look at the "user -> directories" settings next. Is it just the internal directory that is active? Also, could you pick a non-admin user to work with and share their settings here? Not their profile, but the screen the admins use to maintain them (Obscure the name and email if you want)
-
What does the global permissions screen say, and the application access? And what is the installation - Core only, Software, Service Desk, or Software + Service Desk?
-
It's in the project details section in the doc you linked to here.
-
Your velocity variables are not being set - you're doing loads of stuff in java, but there's nothing in there that says "make these variables resulting from the calculation available to the velocity templates" There should be a map object being built with them in a function like "getVelocityParameters"
-
What are you doing in your java code? The variables should be added to the output "map" in there.
-
It depends on the plugin to be honest. Some take different approaches. I wrote one (a long time ago), that simply asked the users in the config "what status in the workflow do you want to consider the end points?" and it had a multi-select list in the config screens. An amendment to that added the question "OR do you want…
-
I don't think there is, but you can just delete everything and then re-add five gadgets (from memory) - assigned to me, watching, introduction, in-progress and project list. I've never been too worried about the defaults.
-
Neither - the default system dashboard already is the default for everyone - you can't create a new default! The system default dashboard defines what people see until they decide they want their own. They can continue to see it even after they start creating their own, and they can use it as a base for their own. The…
-
The standard Atlassian docs do a good job of a step by step guide from what I've read, I've been able to train other Jira admins by saying "read the docs then come back to me when you're stuck" - they do get stuck, but it's always on the more twisted requirements or complex config. >In a project when a specific component…
-
It's gone. You'll need to recreate it from scratch. (It did warn you of this though)
-
That does assume that your permission schemes use "role = administrator" to control project admin access. You may do it other ways (e.g. project lead, group...).
-
Define a filter for "key in (abc-1, abc-7, fred-42)" save it, and use that in a gadget.
-
Hadas, that's really not of any help. Unless you really have products called "magneto" and "gomage", in which case, you should consult the documentation and support for those products. They are not Atlassian products and this is a forum for Atlassian users. Or you're trying to integrate these products with Atlassian stuff?…
-
More detail needed - what application for a start! What type of feed, and how are you "trying to remove a category" and "using a filter"?
-
That can happen when the user Jira is running as can't read/write the directory the file is in or the file itself. Can you check the directory and file permissions on the server for that file? If they are ok and Jira has full read/write, then you might try escaping the \'s in the path - you might need \\ instead of \
-
I cheated - there's a plugin somewhere that adds some counter fields to Jira - one of them is "number of comments", so you can say "number of comments > 0" in your searches. I really should dig it out... Oops - I mean "number of comments = 0" for issues with no comments...
-
Yes, one workflow, but more than one way to look at it, showing only the issues in the relevant status. I should have said that, so thanks for adding it!
-
Not really, it sounds like your process is a bit broken. Having a different workflow for "bug" and "everything else" is a good solution, needs no addons.There's no way to stop items from being added to a sprint either. You can block them from progressing through the workflow with validators (some off-the-shelf, but I'd use…
-
Ok, change the workflow for bugs so that it lands in "to do" instead of whatever you have in backlog.
-
The correct solution here is to stop trying to use two workflows. You've got one process, define that as the workflow. Your other options are * Have two projects, one for backlog, one for development. * Have two issue types, one for backlog, one for development. When you pick stuff to move it from backlog to development,…
-
I think there's a point being missed here - a post-function is not there to control any flow. It's too late for flow control, a post-function is there to do things because you've committed to a path.As a I said already, the name of the current post-function is utterly useless inside the post-function because it will only…
-
I can't think of any use for getting the name of the current post-function in the code. You already know the name because you're in the code already.
-
This sounds like you're asking the same as: https://answers.atlassian.com/questions/9372093
-
A sub task is NOT just a little afterthought on the parent issue, it is a fully fledged issue in its own right. It needs a unique key and to fit in with the rest of the project. It's not "automatic numbering", it's "giving an issue the unique identifier it needs to be useful". So no, because you need it.
-
It's not a problem with JIRA, it's built to treat sub-tasks as issues in their own right with their own sequential number. They display their parent in most places when you need it, so you're not losing anything by having a flat numbering scheme.
-
They do show up with their actual number. Unless you've deliberately turned it off in the subtask diskplay.
-
No, that is done by design. Subtasks simply take the next free issue number in the project. I think I saw a feature request over at jira.atlassian.comto change that scheme but I didn't bookmark it
-
No, there's no way to rearrange the fields, other than the standard ordering in screens. As far as I can tell, Atlassian have no plans to introduce any screen rearranging facilities beyond the simple ordering, as it would be very complex to implement.in Is there any plans to provide a drag and drop capability to place JIRA fields on the View screen. For example, I would like to display fields in three colunms in the Details section rather than two? Is there a pluging that provides this capability? Comment by Nic Brough -Adaptavist- February 2017