Comments
-
I think you've already worked out the best approach - you need a custom field to group issues into queues. I'd be tempted to group up your users into groups with the same name as the queues as well, so that there's a very clear relationship.
-
Check your email server for blocks, blacklists and spam. Atlassian servers generally do try to send mail.
-
Go to admin and change/add the role.
-
Nope, it's still the right answer, but I'll post over at your question as it's more recent...
-
Looks to me like your process does not index the issue that has been updated.
-
There is a plugin that provides an audit log. But you're using OnDemand so you can't install it. I don't think there's anything on OnDemand that would do this, certainly not in the parts exposed to the customer. You'll need to contact OnDemand support to get any further with this (but I wouldn't expect much!)
-
What response? What are you talking about? You haven't mentioned any FAQ before, your question said nothing more than "I want to write some javascript code in the Custom Field configuration, please help me in the same. I am using JIRA 4.4.4." Please, read back properly. Also demanding random examples probably isn't going…
-
Er, yes, you put it in the description of the field. Is that the entire question?
-
You've answered your own question, with a good choice of words! You can put projects into categories. Log in as an admin, and go to Admin -> Projects -> Project categories, and add some. Then go to each project's admin section and select a category for them. I'm afraid it is a single mapping, you can't put a project in…
-
Well, first, this is probably for Ask the CEO about IT service - Webinar with Atlassian co-CEO Mike Cannon-Brookes ? But there is a point I can answer - Atlassian doesn't really have sales people, so there's no one to refer to.
-
I still don't know what you mean by Jira desktop, but if pro-fields won't work, I'd still be tempted to go with the project-metadata. Not sure how you can really prioritise projects though. If you've got one team, then it's easy - you just work on one project until it's done, you don't care about the others. If you have…
-
Very much so.Most people don't seem to need project level fields. For the handful that do, plain JIRA has an addon called "pro fields" which does add some functionality on them, although it might not be what you need, I think it's worth a look before you go into setting up a "project metadata" project.I quite like the…
-
JIRA allows you to create dashboards, to which you add "gadgets". Most of these are reports based on either project or filters, and, of course, you can use filters like "show me all issues that are in projects X, Y and Z", so you can construct all sorts of clever dashboards.Most reporting gadgets are a good jumping-off…
-
You still can't do Kanban with projects - your Kanban boards will only show issues.But yes, I suspect Portfolio will be a good tool to help you with your project planning and prioritisations.
-
JIRA alone covers the first three, but there's no such thing as "project prioritisation in Kanban" - prioritisation is for issues (a project is a collection of issues with something significant in common - like a product, a team or a process). You can inlcude one, many or all projects in a Kanban board. You'll need JIRA…
-
Right. You can't do that, it won't work. Permissions are done at a project level, not issue type. Properties will not support that anyway, they kick in too late in the flow.The closest you can get is to create a "bug" workflow that is deliberately broken - you'll need a validator on the create transition that says "is user…
-
I'm really not sure why you've landed on the use of properties to do this.To disable "Create issue", go to the permission scheme for the project and remove everything from the "create issue" permission. No-one will be able to create an issue (note - check if the permission scheme is shared with other projects before…
-
Why are you trying to do this with properties? The correct way to do it is to use the workflow as it is intended. Could you explain what you are trying to do? (Not the method you're trying to achieve it with, but the actual reason for "disable create and close")
-
It's from a time when JIRA's ecosystem was a lot smaller than it is now. I am pointing out that they said they wanted to fix it and they did, despite taking 9 years about it. If you wanted to compare numbers usefully, you'd do it by "proportion of user base", which at the time would have given it 10 times as many votes.…
-
"Lie" is probably a bit strong. Have a look at https://jira.atlassian.com/browse/JRA-9 if you want a better feel for "we have higher priorities at the moment".
-
That would be it - JIRA is passing in a user that MySQL hasn't been set up to accept. I think your solution is a good one because it's totally locked down.
-
Ok, that's a good test. What does the mysql server logs say about the refused connections?Also, do you have selinux enabled? Try setting it to permissive and try again.
-
The connection to the database is failing - you've either given JIRA the wrong connection string or credentials, or your host setup is blocking the link in some way. Apache is irrelevant at this point, the problem is JIRA and the database, you need to debug that. Could you post the mysql connection setup you are using for…
-
I've used K15t's Backbone to do this several times recently, and iDalko's Exalate in the past.
-
Aliasing is something done at a web-server level, not application. It's nothing to do with JIRA. (Also, it doesn't work most of the time, most applications work with a single url location, and aliases just land on that and use the core url from that point on) All you can do about changing urls in Cloud…
-
You don't really. Your best bet is to talk to your network people. They should be able to tell you if there are any tricks they can support - I've seen two dirty ones which work, but I don't know if they're recommended. One was to use the outgoing proxy server to gateway the connection, so if someone tried to land on the…
-
Depends on how you define your "accessed/opened". The obvious definitions are: * Last updated. Which you've already covered * Last time someone viewed an issue (or maybe the project header). This is pretty much impossible, as there are so many ways you could view an issue, and JIRA logs precisely none of them. Inside JIRA,…
-
Yes. Confluence Questions is an addon for Confluence. Confluence is a separate system to Jira. You can install Confluence on the same server as Jira, add Questions to it, and they'll run together fine as two separate systems. You'll need to make sure the server has the oomph to run both systems at the same time (cpu, disk…
-
No, the whole point of a role is that it goes across all projects. It gets unnecessarily complex if you start trying to limit them to sets of projects. If you don't want to use a role in a project, don't put anyone in it. Just educate your project owners as to which are useful (assuming you've got differing…
-
I think you're going to struggle with that. I'd raise it with Atlassian support to see if they can help. https://support.atlassian.com