Comments
-
Hmm. That is very odd. I can't replicate it on my local install - the field always comes out when it's valid. However, what type of field is it?
-
That suggests that the field is not valid across the entire project. Check the field context in the admin section
-
No. If the field comes out in the issue navigator (which it does, we established that ages ago), then it is indexed correctly.
-
I don't know why you keep talking about tabs - they have nothing to do with the issue navigator. Anyway, these three fields are all standard custom field types and should appear in an excel export if they are appearing in the navigator before you click one of the excel export links. So I'm a bit stuck. They should be…
-
Hmm, so what does it actually say in the type column? (I think you've pasted in my question and not typed an answer over) So, the same filter gives us results on-screen and in XML, but not excel. That implies the field doesn't have an XML output template or is deliberately surpressed (which is why I keep asking about the…
-
I'm afraid that is incorrect. We have already established that the field appears in the issue navigator, and it comes out in the xml, so the question now is why it does not come out in the Excel sheet as well
-
Ok, which type of date is it? Updated, Created, Due, or is it a custom field you have added? If it is a custom field, then what exactly is the type (go to custom fields, and look in the "type" column - it'll say something like "date picker") Also, could you go to the issue navigator with your search. Make sure that at…
-
Tabs only apply to the screens an issue uses. They do no affect the issue navigator or excel output. Could you check that the "missing" field is definitely appearing in the issue navigator and is not shown when you downloadd ALL fields? And, again, could you tell us what type of fields they are?
-
Could you tell us what type of fields they are? (Multi-select, cascading select, etc)
-
You need to create an issue of a type which has a different workflow that does NOT have this post-function on it. Or, you could add a new custom field to the issue type (read only, no need to put it on screen), set it on the primary new issue, and then interrogate it and break oout of the clone process if it is found on…
-
I'm not sure I understand if there's actually a question here - your tags are spot on and answer the posted question in themselves. (A glance at the docs for the blueprint should also give you a lot more on top of confirming your tags are good)
-
You need to be running Frevvo - the plugin allows Frevvo and Confluence to talk to each other, so you need both systems...
-
You can't do it with Field Configuration - if you do, it only makes the first option mandatory, and lets the user leave the cascaded part empty. You'll need a validator that can check the second cascaded part of the field. I don't know if the JSU does that.
-
Right, this is a good case of compatibility failure.Confluence 3.5 does not support IE9, it's not compatible (the effort to make it so is a waste of time, as IE is so riddled with bugs and incompatibilities)Your options break down to:- Use IE8 (really very very very bad option, as it's a failure on standard compatibility,…
-
What version of IE are you using? And my tired old eyes aren't sure about the version of Confluence they are reading from the screenshot - is that 3.5.13?
-
For Cloud, there's no concept of "test" - a Cloud system is a Cloud system. You can use it for whatever you want! So, if you set up two Cloud accounts, one production and one test, you can work in them separately, but your options to transfer between them are very limited - you'll be doing config and setup mostly by hand…
-
Estimation units are done by board, not issue type. It doesn't make any sense to do them separately by type - "my story is 4 story points, but I've got a task which will take 2 days" renders them incomparable.
-
<sigh> http://confluence.atlassian.com/display/CONFKB/Wiki+markup+tab+no+longer+exists+in+Confluence+4.0. The main point of version 4 was that Atlassian were killing off wiki markup.
-
Yes. Just make sure their data sets are completely separate (separate databases as you say) The only drawback is the loss of both systems if you need to do maintenance on the database.
-
Check the notification scheme is set to send to the right poeple on the updates you are making. If you are testing it with your own account, check your profile is set to say "notify me on my own changes", or it won't send to you.
-
No, javascript is even more restricted in Cloud than it is in server to prevent people doing bad things with it.
-
First, create a Jelly script that does the job when you run it as an admin in the foreground. The basics of enabling Jelly and where to run them is at the top of https://confluence.atlassian.com/display/JIRA/Jelly+Tags - skim that, and then look further down, specifically for "Jira:CreateIssue" Once you have a script that…
-
Your wiki markup is wrong - put a space between the # and the rest of the line. Also, check around the field - if you have the configuration right, wiki fields will have a preview and help icons (small) nearby
-
I use the meta data searches. For example "filesize:[1024 TO 2048]" will find attachments between 1k and 2k in size. Setting the first number to say 1Meg, and the second number to something astronomical is an excellent starting point for "hunt the chunky attachment". This trick supports searching created/modified dates for…
-
Correct, there is no validator in the off-the-shelf version that will do what you need. You will need a plugin (or possibly some javascript) I'd be tempted to try https://marketplace.atlassian.com/plugins/ru.mail.jira.plugins.uniqueregexfield although there are other plugins that might be of help too.
-
Just to fully explain that - you need to find or write a "validator" that will check the input matches the format you want to force on that field. Or you could write a field *type* that encapsulates the function (a bit like the way a date or number field will only accept certain inputs) Sara is suggesting the second and…
-
JIRA Core really is the core of JIRA. There is nothing to "enable" - you just upgrade from 6.4.2 to 7.x and that's it, you have JIRA Core, with all your data. JIRA Software can be added later, but if you already use the Agile add-on, I'd strongly recommend upgrading from JIRA 6 + Agile to JIRA Software.
-
Start with https://confluence.atlassian.com/jirasoftwarecloud/getting-started-with-jira-software-764477795.html Although: * Try clicking "log in" on any JIRA page * Log in as an admin and click projects -> create * Once you have a project, look for project settings at the bottom left, then "roles" when you've gone into that
-
Workflows are not stored in a format that will let you extract it with plain SQL.
-
Yes, that's the scale. I can't explain it, I'm not the vendor. For add-ons, youhave to pay for the number that matches the largest number of users you have for an application. (For example, if you have 3 Agents, 25 Software users and 10 Core users, while you have 38 users, you need to licence add-ons for 25)