Comments
-
Ok, but that leaves us in a dead-end. If the field is on-screen, the scheme associated, and you have set-security permission, then the field appears on create and edit. Even if you have no levels in it, it appears (with a single option of "none"). So I'm stuck.
-
You don't mention if you have associated the scheme with the project?
-
How consistent is this? Is it for every project, and when you create a new project, does it always happen to the same settings screens (i.e. always request type)? What does the log say the error is? If you are behind a proxy, does that show error logs when you do this?
-
Um, you're looking at documentation for JIRA 6, but you appear to be on 7. Try the application access, and/or typing "licence" into the admin search next to "Administration"
-
I'm afraid versions are (still) project level artefacts, they don't go across projects like that.
-
Ok, and there's no email at all arriving on create? Do you have "email me on my issue updates" enabled in your profile?
-
No, the sub-tasks are there as a part of the parent issue. So they need to take the same security level, as they're a tightly-coupled fragment of the issue.
-
That's the bit I can't judge, I simply don't know how big your code base is, how good the network connection from the source machine to the Bitbucket repos might be, and so-on.
-
Yes, you need to upgrade JIRA's Core installation.
-
Cloud shouldn't affect it at all. You did publish the new workflow too? (That's the one I forget all the time) Also, what template did you use for the event notification?
-
When they log into Confluence or JIRA? And are they customers or full JIRA/Confluence users?
-
Which transition(s) did you change the event fired on? Are you sure you are going through one of them? (As "create" usually fires "created issue", and most of us don't change that one)
-
The screen you surrounded with the red box has no (xxxx) after it. That means that particular screen is not in use as a transition or issue screen. Look to the one below it instead, as that is in use.
-
It's probably the same problem as discussed above. What does your log file say the problem is? Are there emails it can't delete in the mailbox?
-
There is no syntax for it, JQL for the custom field is built to look for values, not count up values. I'd use one of the scripting add-ons to create a simple scripted field that displays "number of labels" as a numeric, so you can search and sort on that. Don't even need to put it on the issue screens, as it's for…
-
>How can I find out which firewall ports need to be open Assuming you want to use the systems raw, on their current ports (which means your users will be using urls with ports named in them, like https://ourjira.ourcompany:8080 ), then, while the applications are running a simple netstat -plant will list all open listening…
-
Not within the application. A couple of places I've been to throw up a simple static web page with a list of the portals available so people can jump to them. Or if you want different urls, a page for each with an instant re-direct to the relevant portal.
-
I was looking for the "user picker (multi)" bit really, but that's fine, I was worried that it was some odd field type that might be hiding itself, but that's ruled out that! The box you've got in red tells me that the screen "Needs Review" is not in use though.
-
It depends on what port you choose to run it on. The default is 8080, but a lot of us relocate it. Often with proxy throwing it over to a standard port, so the users and urls aren't required to give the port every time (As an example, almost all browsers assume port 80 if you use http in the urls, and port 443 if it's…
-
Ok, what type of field is "reviewer"? Look in the list of custom fields and look at the type usually just underneath the field name.
-
Incoming ports only need to have the port you want users to access JIRA on. Outgoing - depends on what you want to connect JIRA to - SMTP, IMAP, POP, other Atlassian stuff like Hipchat, Bitbucket or Confluence etc. They all run on other ports, so you'll be needing to allow JIRA to go out over them
-
I'm really not sure, I don't know why it would work in one OS and not another. Are there other differences between the two systems?
-
I'm afraid that's not currently possible in the UI. You can hack it in the database, but I can't recommend that, and I'm not sure if it might break things (other than saved filters, which it definitely will)
-
Lithium (this forum software) adds some dodgy characters to the end of urls sometimes - follow the link again and remove everything from the url after the ".html" - it will usually have .html%A0something I've explained instead of edited because you might run into at again on other questions!
-
Yes that is what they have said. They want a unit-less progress bar. There is a refusal to provide a useful definition of "progress", which is, as you yourself point out, utterly useless
-
Ahh, nicely spotted. I think you might need to escape it in the url.
-
Because that's what the posters above explicitly stated - they wanted a percentage complete without defining what it meant. Which is useless. You don't have to put a unit on it on-screen, the point is that 80% of <i don't know> is useless.
-
Two easy options: 1. Remove the post-function that is setting the resolution to "fixed", and add in a transition screen with just the resolution on it. JIRA will pop a box to let them select one 2. If you're ok with a default to "fixed" (or some other value you could change it to) being done by the post-function, but want…
-
I'm afraid there's nothing new.
-
Ok. There's no question or useful description of a problem here?