Comments
-
Well, I'm sure an SQL expert could do it, given the schema, but it would be complex and messy. First, you need to separate out "system" and "custom" fields. System fields are more simple - they automatically belong to all projects. The complexity is finding out whether they are used. To do that, you'd need to check the…
-
Not really, the UI is the most friendly way of finding them out, because the data is complex. An SQL query would give you the right answer, but in an even less friendly format than the UI.
-
You do NOT set a custom field value in a scripted field, those are mutually incompatible things. Are you trying to use a scripted custom field, OR are you trying to set the value of a custom field that can hold data?
-
You can't change a user's login id, but an administrator should see a link to "administrate user" on the users profile and you'll be able to change their display name. (They can also change their own name)
-
If it's issue information (content on the dashboard), change the issues and refresh the dashboard. If it's the dashboard settings, well, um, edit the dashboard settings.
-
Argh. Set up a screen scheme, as we keep telling you. To keep it really simple, do this * Create a new screen called something like bugcreates, and add two fields to it - summary and your custom field * Create a new screen scheme, called say bugss * Add a line to the new screen scheme, saying CREATE = bugcreates, leave the…
-
Ah, I see one of your duplicates has been answered.
-
As we've told you before, you tell jira which SCREEN to use for CREATE by using the screen scheme.
-
Yes, I thought there might be more detail behind it. The case I outlined needs no code, and hence works well for some of my clients, but I think you need something more clever. Which means a Listener.
-
You can do something along these lines. * Change your permission scheme so that it allows "browse" rights to "user custom field" * Change your notification scheme so that "Create" sends mail to "user custom field" They should get the mail that all the other users get on creation. For something more flexible, yes, you'll…
-
Not natively, but have a look in the marketplace for the Survey macro.
-
A service desk layers itself over a project. Your other project is not a service desk project, so it doesn't appear in the service desk stuff. You can give your agents access to see it as a normal JIRA project of course, but it's not service desk.
-
>I go into edit task and assign it to Joe and change workflow to QA This is very unclear to me, I need to translate it into JIRA-speak, and go over precisely what is happening. So. 1) You have a QA task in Eugene's column 1.1 Just to confirm, "QA task" is an issue type? 1.2 What is the status of that issue? 2) You go to…
-
It's point 2. You're moving issues into "In QA", and that is not in a column on your board. (Apologies for pointing to the left - it seems Cloud JIRA has moved the unmapped status to the right in a recent version)
-
This sounds really odd, given 12 years of JIRA, but I can't read the search in your first screenshot. Project = Tap Analytics, but the last bit, I don't know. Three questions, if I may? In your second screenshot: 1. could you click the "board" button, and then go to "general". Your board filter will be there in JQL - could…
-
Your board filter is excluding them (check Board -> Config -> General and read the filter), or they are being moved to a status that is not in one of your board columns.
-
Thanks Udo, I really couldn't remember (except for comments, I know those work on multiple columns)
-
No. Reporter is a single data field, you can only put a single user in there. For fields that can hold multiple data, you should be able to map multiple columns (but I am not 100% sure of that because the last time I was importing CSV, it was a hacked importer, so that might have been a feature of that importere)
-
JIRA Agile is not available for JIRA 7 and above. It has been re-structured as an "application" called JIRA Software new (that adds Boards instead of Agile into your menu). The functions you had in Agile are almost entirely the same as what you now have in JIRA Software. To see if you have that, look in "manage…
-
No, but sort of, but yes. The Jira home directory can be anywhere you want it. The only rule is that the Jira service *must* be able to read/write it in full. The attachments must be underneath that. Now, if you're on a Unix based operating system, you can do all sorts of clever things with great ease... symbolic links,…
-
Hmm. Definitely need to do some debugging on it then. I'd increase the logging to see what is arriving in the POP mailbox (also, what does "not work" actually mean? Mail not incoming at all, processed incorrectly etc) As far as I know, a trial is pretty much identical to what you'd see if you decided to buy. Most of the…
-
For some of your points: 1) Check what you're "redirecting", it might not be redirecting at all - you'll need to dig through the settings and logs to find out what it's really doing. I'd start with the settings in the Jira email handler, it might be seeing the mail as bulk stuff to be ignored. 2) Jira looks at the from…
-
Correct. You will need to read the workflow yourself to work out what the end states might be. It's perfectly possible for a human to write a workflow that looks like "Badger -> Mushroom -> Snake". This example shows you a number of problems: * As another human, you'll probably be able to work out what the end state might…
-
Yes, you need to look up what is available, as the id is variable.
-
It depends. The id of a transition is part of a workflow. If your issues are configured to use the same workflow, then of course the transition will have the same ID, because it's the same workflow. If they're using different workflows, then no. (If you've copied workflows, similar transitions might have the same id, but…
-
What documentation are you following, and what do you get when you try it? I.e, what's missing on your screens compared with the documentation?
-
Although, I've just looked at your error message properly - the problem is the Fisheye/Crucible server got disconnected fro the Subversion server - that's probably a networking or Subversion problem rather than Fecru. Check the logs on both the Fecru server and Subversion to see what they think has gone wrong in more…
-
Although the indexing has failed, you should still be able to get to the Fisheye/Crucible admin screens and find the licence details, which will include a SEN. You should then use that while raising a support call at https://support.atlassian.com
-
You might want to explain what TMG is, what it does and how you've got it configured currently. Typing TMG into Google refers me to criminal record background checks, but I assume it's some server or service you've got that does something to do with user access?
-
I'm afraid re-stating your question does not change the answer. You can't put the validation on edit in the UI, you need to move it down into the workflow, or use javascript.