Comments
-
You simply can't do this. You need a way to indicate that a user is a "team lead", but that data is not related to issues, it belongs to people. Filters are for issues, so it's not going to happen. There's some clever trickery you could do to get there, but frankly, I wouldn't bother. I'd simply create the dashboard with…
-
Create a *system* dashboard that includes the gadgets you need. The project level stuff is a step away from the dashboard, and there's two steps you need to think about. 1. A dashboard can contain anything you want it to, but most of the gadgets you can add rely heavily on filters. So put the gadgets you want on the system…
-
Not directly - when you create an issue, it always takes on the first state in the workflow. That does lead you on to the standard approach - take the workflow you are using for the parent issues, copy it and change it for the sub-tasks, changing the entry point from "backlog" to whatever is most apropriate. If you've got…
-
I'm afraid not, you'll need to write/configure your quick filters each time. I'd have a look at swimlane by assignee too, that might help?
-
Yup, this is one that the community would be very interested in, across the whole set of Atlassian products. (I suspect MySQL is the second most used database for the suite and people are getting increasingly interested in keeping it free and open) I'll vote as soon as I spot them...
-
Copy it is the short answer. Although, if your source confluence is broken, it's quite possible that the config and/or data is damaged or wrong, so it might not help you that much. You probably need to work out what is wrong there before copying data.
-
Your system info page should tell you what files you've changed away from the base distribution, but I suspect you'll find the log file will tell you more useful information about this error.
-
You do not. You won't get any access to the Cloud databases.
-
The only clean way to do it is remove the user's access to JIRA Software.
-
Ah, this is the problem with working from memory. Sorry. Set Field Value == Update Issue Field
-
Unless your admin has completely disabled it somehow, then I can guarantee you that it's there. If it's not, then you should be seeing problems with your resolutions not being cleared when you re-open issues. Where are you looking?
-
There should be a post function called "set field value" - that will offer you "assignee" as one of the fields.
-
Ah, good, that's easy - add a post-function to the workflow create transition that says "set assignee = X"
-
Always set it to the same person? Or just set the default and allow users to override it?
-
The participants field is coded to say "reporter, assignee and anyone who has commented on the issue". It doesn't scan for "used a transition" or "Edit". I've used the participants field code as a base for other similar fields a few times now (e.g. reporter, commenters and person who changed priority), but I'm afraid the…
-
Sorry, disk space? What's that got to do with it? Did you identify an error occurring because it was out of disk space?The fact you're getting this bundle error implies you've not looked at the document I pointed you at originally - what in there have you done?
-
That's JIRA running low on resources while trying to start up. Take a look at https://confluence.atlassian.com/display/JIRAKB/JIRA+System+Plugin+Timeout+While+Waiting+for+Plugins+to+Enable
-
It's really nowhere near as complex as that. A permission scheme defines who can see and do things in a project that uses it. A group is a batch of users, which you can use in schemes. As an administrator, you can create and delete groups, add and remove users from groups, add and remove permission schemes, and associate…
-
I find it more simple to start with groups. Once you are happy with using groups in permission schemes (and notification schemes and so-on), then you can move on to roles. Roles are nicer than groups because * They are a project thing. * You can delegate ownership to your project teams * You can reuse the same permissions,…
-
I think Jerome means "do not apply a scheme to your project until you are sure it is correct" I keep a "test" project in my Live systems, simply so I can test this sort of stuff. Mess with a copy of your scheme, apply it to the test project, test it with the test accounts, and only then, apply it to the real live projects…
-
Do you have the option to create testing accounts? (Temporarily if you have license limits) They can be really helpful when you're testing permissions. Don't actually do anything with them other than log in and look around the projects you're working with of course. One other thing about permissions - don't be scared to…
-
I don't understand why people struggle with permissions. Barring the "reporter browse" permission, they couldn't actually be any more simple. Group/role X can do Y. It's simple.
-
I see what you mean about the labels - JIRA is right, but servicedesk may be misleading. I'd drop those two and add web_helpdesk and live_person.That's unless you mean "Could I move to JIRA Service Desk and drop Web Helpdesk and/or Live Person"?FWIW, I've not seen any specific integration between them, but JIRA does have a…
-
Yes, there's a number of ways to do it. I prefer getting Agile so I don't have to code for any of them
-
Um, ok, you flagged it with Agile, so I thought you had. There are no tools that will re-number like that. The problem with the basic idea is that if you number them 1, 2, 3 etc, when someone needs an insert, you have to re-write all the lower issues. In a system with tens of thousands of issues, that's an immediate fail.…
-
Priority is a fixed length list of possible options, so if you've got 20 of them, you run out when you've got 20 issues. What you need is "ranking". This is implemented by Agile/JIRA Software, just make sure you have one single global rank field (you can have more, but it gets messy)
-
Ok, that's good, and the screenshots are very clear too. You definitely need to check the field configuration to see if the system priority field is valid for the filter you are running. There's actually a really quick and dirty test here - find an issue that has a priority set (check the issue view) and then run a filter…
-
Is the field a custom field, or the built-in priority? Is the field valid for all projects? (For the system field, check the field configurations, for a custom field, check those and the field context)
-
Use the issue transitions to move the issue through your workflow.
-
No. JQL is for finding issues. Not reporting the data in them. You'll need to find or write something that can "pull" the relevant data and display it.