Comments
-
No, transitions in the workflow must have distinct names. You could try using an extra space ("do_something" and "do__something"), or punctuation and capitalisation ( Do Something and do something.)
-
What user list system are you using? Internal, LDAP, external Crowd, etc?
-
Have a look at the "field configuration" for the project//issue type. Check that your field's "renderer" is set to something other than "plain text"
-
Ideally, you should use the UPM to install new add-ons, not an upload. I don't know why you're expecting a click to execute it - add-ons run inside JIRA, not standalone. For an upload, you should be using "upload" from the manage add-ons page, and there's nothing to click and run there either. .jar files can be "run" if…
-
Took me a while to find it when I upgraded too :-)
-
You have to be using a recent version of Jira. You need to look in the permission scheme for the project(s) and make sure people fall into the permission "View Read-Only Workflow"
-
This is probably the bug Microsoft introduced recently. With the blank sheet, go to File -> Options -> Trust Centre -> Trust Centre Settings -> Protected View and un-tick the "enable protected view for files from the internet" It's a nice six-legged "feature" from MS - technically, not a bad security idea, but there's no…
-
Depends on the version. In older versions, the remote API is enabled by default, but if you have chosen to turn it off, Cody's answer is spot-on In more recent versions, JIRA relies on it internally, so you can't turn it off, it's always there.
-
The standard cascading select in JIRA is only two levels. You'll need an addon to provide 3 or more layers (look for the multi-level cascading select in the marketplace) The other option is to try to relate separate select lists together - this involves vile javascript which usually fails, or I think you can do it with…
-
You need to tell us what you've tried really. Personally, I'd take a different approach and edit the actual text that's coming through - https://developer.atlassian.com/display/JIRADEV/Customizing+Text
-
It very much sounds like it. Are the two settings definitely pointing at completely different schema?
-
That's not really much to do with the database, it's telling you the authentication stuff is broken. You don't need anything special for your situation (many places run one database with several applications using it for their data store) You probably need to look into the log a bit more. But have a look at…
-
If you were on Jira standalone, it's possible to hack the link off the screen. That won't stop someone who knows the url from using it, but makes it hard. I don't think you have that level of access in OnDemand.
-
Ok, the file: approach will only work if your browser understands the type of url, and it can open the file of that type (or has been configured to open it in another application) The main problem with using local files is that your users all have to use exactly the same path structure - it's one of the reasons that…
-
Ok, then you'll need all of your users to be using identical paths on their machines, and you can put in a url of format file://path/to/the/data Obviously, you will also need to have some way of replicating all the files across those client machines too.
-
Sorry for the delay, Answers has been flaky recently. I'm afraid you need to tell us what "local" means. Does it mean "local on the JIRA server", "local on the client machine"?
-
Could you explain what "local" means here? Do you mean files on the JIRA server, on another server or on your client machine?
-
How have you implemented "test cases"? (There's lots of ways to do test cases in JIRA, we need to know how you're doing it)
-
Instinctively.... * No, JIRA does not change team lead on its own. It needs a human to do it * (That said... Scripting and plugins can, of course, be written to do this, although they'll still need to run as an admin account) * JIRA doesn't normally log this stuff. However, I think the admin audit log does capture project…
-
If you're on Cloud, you don't. You have no access to the environment (and shouldn't), so you can't add anything. If you're on the server version, generally you'd add them to setenv.sh or setenv.bat Or do you mean something else by "environment variable"?
-
The page properties will show "incoming links" as a quick fix, but I think you need to go one further and install one of the "incoming links" macros you can find in the marketplace
-
Ah, ok, that's more clear. It actually sounds broken to me - your users are in a group together, and that group is nominated as an administrator group. They should both have admin rights. I'd double check all the groups that admin and userxyz belong to, but it's sounding like it's broken. Or, possibly, OnDemand works…
-
Er, no, you have to be logged in as an administrator to add projects. That's what being part of the administrators group is - it makes you an administrator.
-
That's not quite what I asked, although I think it might be just the way you've phrased the answer. To rule out my misunderstanding - when you visit "Admin -> Global permissions", what groups have "administration" access. There's two admin levels, both of which can create projects, so the membership of one or both is…
-
Yes, but check the groups VERY carefully - you need to be certain that the group "admionistrators" has admin rights (see global permissions to check that) and that it is shown as "a group I am in" when the user visits their profile.
-
Not sure why you think it's in the Agile project menu - the screenshot shows an old version of JIRA and the calendar appearing in the JIRA project tab. In the latest version, it should still appear in the project bar. It's also available as a gadget.
-
Sorry, I was not clear. With OnDemand, you CAN use the REST services. What you can not do is write your own plugins or scripts for automation and so-on and install them - that's why I only mentioned email and REST as possible options - other stuff is ruled out by OnDemand, but you can help yourself to the REST stuff!
-
@Thomas-S has a good point, you do need to be careful with email if data is going both ways. REST is a standard way to expose functions that systems can perform to other computer systems. Rather than waffle at random, or generalise, have a look at how it works within Jira - this doc is focussed on Jira, of course, but…
-
There's a couple of options available (you've said OnDemand, which cuts the list down a bit) First, Jira can send and receive email. I don't know Gemini, so I don't know if this can help, but you can configure Jira such that * It can send email to an address for Gemini to pick up and process on all your comments * It can…
-
You'll need to report that to the owners of the site, it's not really a Confluence issue. Although, if you think Atlassian should remove dead links from the docs, we don't really have a formal way to tell them - they pick up here sometimes, but the only reliable way is to raise a support issue saying "docs are wrong" over…