Comments
-
You don't need any plugins. Look at your "screen scheme", in there, you'll find you can tell Jira to use different "screens" for Create, Edit and View. A screen is a list of fields to present to the user. Generally, most schemes use the same screen for everything, to keep it simple, but you can change this. For your case,…
-
You don't. Scripted fields are data that results from a calculation based on existing data. On the create screen Price1 and Price2 are not set, so the script cannot do anything with them. It can only create the data as the issue is created - after the user commits the creation data. The other point about scripted fields is…
-
First, restart it - it's obviously hung. Secondly, look at your log file - what does that say?
-
The issue-statistics gadget requires fields that have lists of possible options. Lists of users, select lists, radio-buttons, components - all of these are lists of options. But strings, numbers and dates are not - they have effectively infinite unbounded options, and hence, are not suitable for the gadget. You could, in…
-
It is. JIRA software is an application that runs on top of Core, so you always have Core there (along with it's ability to import backups from other JIRA systems)
-
Yes, I know. It's a licensing thing - the ability to connect to exchange natively apparently costs more than most pay for JIRA in the first place. I'd be looking to move to a provider who will give you proper email boxes.
-
I'm afraid you'll need to find a way to make it IMAP or POP enabled.
-
Ok, that might not be an add-on. You need to ensure Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 28,800,010 milliseconds ago. The last packet sent successfully to the server was 28,802,419 milliseconds ago. is longer than the server configured…
-
I don't have the time or energy to guess my way throgh your whole log file. What does it say at the time of the backup failure?
-
Best guess is that you've got an invalid or removed add-on that still has data lying around. Have a look at the list of add-ons you have - any showing as broken, invalid or disabled? What does the log file say at the time of the backup failure? I'd expect it to tell us what classes are failing, which would at least lead us…
-
You've put a transition in your workflow called "reset". You'll need to talk to your administrators to find out what it's for and why they've done it.
-
Where in JIRA are you seeing this?
-
You'll need a post-function to do that during a transition. You might want to write one for yourself or maybe use the script-runner plugin (it provides a framework and hooks for you to write stuff like this and saves you having to write things from scratch)
-
You'll need to explain the context of this question
-
I think you've misunderstood the question. The rights to edit a workflow are limited to Jira Administrators. It's nothing to do with security schemes.
-
Editing workflows really really should be limited to people who understand Jira. Project leads mostly do not know it well enough. Anyway, there is one option - do you have the Agile addon? That would let the project lead use "simplified workflow" - they set up a board and the workflow follows the board. No editing rights…
-
Additionally, I'd strongly advise you not to do it. The Jira administrator group should be a small group of people who work together closely. Most of my engagements with Jira have started with "we need to clean up the mess made by letting project leads have admin access"
-
I'm sure you could invest a few hours in writing a report or running some SQL, but the quickest way to do it is simply look at the admin screens that list them. (One of our admins wrote a curl get and really simple text processing script to do something similar, took 10 minutes)
-
Change the "field configuration" for the project. You can hide fields in there completely. https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour
-
You can only share with groups that you belong to. Add yourself to the group and share the dashboard.
-
You've (re)started JIRA as the wrong user, either last time you ran it or this time. The user running it takes ownership of files and always assumes the files are theirs, so if you run it as another user, the permissions are usually wrong. Stop JIRA, change the ownership of all the directories (JIRA home and JIRA…
-
"Can't" doesn't tell us what the symptoms are - could you explain more please?
-
No, the description field is text, it takes a single value You need to merge your two columns into one in your CSV, then you'll be able to import the results.
-
Well, if you read the previous answers... The subversion tab is for subversion. The commits tab is for linking to other source code tools.
-
I don't understand what you're asking now.
-
The commits tab is for linking to other source code tools.
-
The commits tab is nothing to do with Subversion, you need to be looking at the Subversion tabHowever, your log file is very clear - the subversion index is, at the very least, broken. From that error, it's probably non-existent.I would:1. Stop JIRA2. Remove the directory…
-
The way the plugin works is that it indexes your repository and looks for the keys of any Jira issues in the commit messages.So, to get them to appear, you need to ensure your commit messages include the issue references.If you don't get this tab appearing, then the plugin may not have enabled correctly. So, the things to…
-
What's an IHM? What docmentation have you followed for installing the addon, and what have you done differently from what it says? What does your log file say after you install/enable the plugin?
-
Edit the workflow - see https://confluence.atlassian.com/jira/configuring-workflow-185729632.html