Comments
-
You're right in that you need a plugin - off-the-shelf, Jira doesn't have a validator to do this, but there are quite a few plugins that provide it. All the ones I've tried work fine, but they're all part of bigger plugins, so it's more a case of finding a plugin that may have other things you want to use as well, and use…
-
I am unclear on what you mean by "Query template". If you go into the search screens, you type a search in (or select if you use simple search) and it searches. I'm guessing you want some predefined queries which users can then adjust to their own needs? That's not something JIRA really provides, but it's easy to stick…
-
You'll need to find or write something to extract the data. A "JIRA Query" as you put it returns a list of issues, it doesn't have anything to say about the data on them. You need to find/write a report that tcan take a list of issues and display that data for you.
-
My understanding is that it's not even an add-on. All the core code for data-centre is buried and dormant within a standard JIRA installation. It doesn't do anything until you apply a data-centre licence, and then it wakes up and starts accepting config for your nodes! It's been a few months since I looked at a DC install,…
-
Yes, you can, the licences are easy to swap around
-
I think you've got it right actually. Upgrade to JIRA Software 7.0.10, then get production on to data-centre, and build test systems as required. Your test environments don't need to be data-centre unless you're specifically testing the data-centre capabilities - JIRA Software is functionally the same on the surface…
-
There are no built-in script functions for priority changes in JIRA. Do you mean one of the scripting add-ons? (If so, which one? Also, versions would be handy and a note of which docs are you following?)
-
Er, have you read my last statement? Look at the support managers view. And remember that this decision *has* been "regulated by Atlassian/JIRA developers". And they've said "no"
-
That's the point - the "handful of users that would do any harm" are going to make mistakes that chew up a disproportionate amount of support time. The calculated risk here is "massive big red expensive thing". You really need to consider this from a support manager's point of view instead of the user. Try it - you'll find…
-
Message fields are in the Jira Toolit plugin. Make sure that's enabled in your Atlassian account and then the next time you add a custom field, you should see "message field" on the list of types. Mandatory fields are set in "field configurations". They will not actually help you here though - you've reminded me that you…
-
No, it's completely the opposite. Think of it this way, you go to a meeting with your boss and say "I'd like to allow our users to inflict massive damage on their system, with us having to pick up the pieces when they do? For free". No-one in their right mind would take that gamble.
-
Large numbers of support tickets generated by allowing people to make (potentially catastrophic) mistakes simply is not supportable. I've worked with the script runner a lot. In most cases, it's great. But when you get a combination of the script-runner (or other clever plugins) and an inexperienced admin, you end up…
-
Atlassian don't have the resources to support every single plugin their users *might* want to install. OnDemand is set up to be supportable, so they have to limit the range of plugins to ones they know they can support. I completely understand their exclusion of the script runner though. It's a good, flexible, well…
-
The forums were shut down, I'm not sure Renjith has re-posted the same answer anywhere. Also, this is quite old and it relies on the "velocity processed message" fields from the Jira toolkit, which aren't there any more. The principle is similar though - you can use a "message field" to tell the user that they cannot…
-
I know there's a lot of interface changes in 5, but I've not really worked with v5 seriously yet. The "edit message" field though - that comes from the Jira Toolkit plugin (which is one of a handful of plugins that are so useful, I struggle to use Jira without them)
-
Um, we just said you can't do it on screens without some code. REST will respect the permissions in Jira, but as this isn't something you can do in Jira, there won't be anything in REST (again, without coding)
-
This isn't available. There are some workarounds, involving javascript or workflow tricks to prevent users actually committing an issue they shouldn't, and I've seen some hacks in code that do it, but it's not a standard function.
-
I don't think you can do it - the sprints belong to the main board, so the others don't show them until they start to matter to the owners of the other boards.
-
It can't be used with OnDemand. There's a limited list of add-ons you can use in OnDemand, and you control them via your OnDemadn account. See https://confluence.atlassian.com/pages/viewpage.action?pageId=315326753- I'm afraid poker is not on the list
-
Correct. The main argument from Atlassian I've heard is that Confluence is there for collaboration, and you generally want to work together on everything.One common trick is to:Grant "create" to everyone who should be able to edit your pagesPut a restriction on the "home" page to limit edit to yourself and people who…
-
You have to grant them "add/edit" at a space level, then restrict the other pages in the space.
-
In both cases, no. You could hack the templates that render the descriptions, and the templates for editing them, but you may also need to change the database columns that they are stored in. Quite difficult to do safely and a pain in the neck on upgrade. You might be able to inject javascript to replace the text though.
-
Start at https://confluence.atlassian.com/jirakb/troubleshooting-jira-startup-failed-error-394464512.html
-
The description of the problem makes me think something is broken. The task issue type missing should be irrelevant, although it does suggest that your installation went wrong because it should always be there on a new system (you actively have to rename or delete it after a clean install if you want rid of it) What does…
-
Ah, right. That's not going to happen. You can't downgrade Jira data like that. Changing the build number is not enough. You need to undo ALL the changes that the upgrade process as made. 4.1 to 4.4 is not huge, but it's big enough that you could spend weeks trying to get any downgrade right. I'd suggest you either go to…
-
First, you need to be certain that it is safe to roll the number back. Why has your data got into this state? If it's been upgraded by a later version of Jira, then rolling the number back is simply going to break it, you're wasting your time. Second, if you're sure it's safe, then the build number is in the propertyentry…
-
Um, this is a follow-on question as https://answers.atlassian.com/questions/73055/auto-routing-of-issues-based-on-rules Talking about "issue routing" without the context is unclear - Savitri is looking for ways to handle automatic assigning of issues to people. The previous question mentioned the built-in…
-
That's not going to work as a reply as it doesn't contain the JIRA issue references required to tell JIRA which request they are talking about. In fact, I'd expect that to be creating new requests in Service Desk. If it's not, then take a look through…
-
What is the format of the emails Zendesk is sending to Jira? Is it in a form JIRA can process?
-
How are your columns mapped to the actual status in the mapping for the board?