Comments
-
You can't. A field is either mandatory or optional. This is set by the field configuration for the project/issue-type and does not get any more granular. If a field is mandatory, it's mandatory on create, edit and all transitions. End of story, for Jira off-the-shelf. Of course, there are options You may add plugins that…
-
Support issues are private - we can't see them. I suspect you're using a theme or plugin that isn't in use in the other people's Confluence. A green down-arrow rings a bell with me from when I was at a site using Webdav for attachments - could that be it?
-
I'm afraid not, plain JIRA still has a single global hours-per-day setting. The only workarounds are the ones you fear - install plugins that can handle it.
-
Look in the JVM section of the page.
-
Go to admin -> system info to find all that and more
-
If a user picks the wrong field, they should know straight away, because it will be empty, or even not appear for them at all. If they are worried about picking the wrong field, then it's likely that you have fields with very similar names doing the same thing, in which case you should really be sharing the fields, not…
-
You can't. It's a bad idea too I'm afraid. The whole point of the issue navigator is that it's flexible and fast. I wouldn't want to have to muck around re-adding columns because the last search removed them because I happened to include a project in the query. Nor would I want to have to deal with the users asking "I…
-
Ah, good, so you were editing the plain text templates, and receiving html emails?
-
Your profile has a setting for getting emails in plain text or html. Make sure yours is set to text
-
Ok, that looks good. Some more debugging (apologies if some of these seem obvious, but if I don't ask the full set, we might miss something) * When you create the issue, do you fill in field 10007 with any data? * When you altered the properties file, did you restart JIRA? * I'm not 100% sure that the velocity caching…
-
If you've followed the docs, then the field will be there in the email. So, trace through what you are doing in full - which files, what type of email, was the field filled etc. Try some basic debugging - try sticking plain text in the template - does that come out?
-
I'm afraid "it doesn't work" tells us nothing about what might have gone wrong.
-
I'm not sure what is unclear in those docs. You have to find every file that generates part of the body of an email where you want to include the field and add the required code for your field to it.
-
Yes, it's covered in the document I pointed to.
-
See https://confluence.atlassian.com/adminjiraserver071/customizing-email-content-802592932.html
-
No. This is the same explanation as the question you asked about automatic assignees earlier at https://answers.atlassian.com/questions/876/manage-automatic-assignee . The basic principle is that groups are collections of users, and not an individual like users are. Component leads are users and hence the same logic…
-
Yes, but you won't get access to the logs. If you're having mail problems, it probably won't be JIRA Cloud, but the best thing to do is raise the issue with Atlassian Support
-
It sounds like you've answered your own question here. If you set the permission scheme to say "edit/delete own comments" for users, then that's all you need. Even if you set it to "anyone", it will do the job - Alice will only be able to amend comments made by Alice, Bob will only be able to modify Bob's comments and…
-
You can't. Jira doesn't support this in any way. As you've already said, you have to do it in Apache or Firewall. I suspect you can write custom code around the user handling in Jira (or rather, Crowd) too, but it wouldn't be pretty. For OnDemand, I don't know if Atlassian would support this request and modify their…
-
You said you have an error when running JIRA. (It's a colloquialism to say "it fell over", but it means "the error"). Then you posted a part of your log ( missing the rest of it which might help us), and you have not described any of the symptoms of the error. /We can't help you unless you explain what is wrong. Imagine…
-
Please, read the answer above.
-
Why are you messing around with ports when your error has nothing to do with them.
-
The UI usually runs on port 8090, unless you've changed it. But the ports wouldn't cause that error.
-
You're going to need to explain what you're running, where it falls over and how you installed it.
-
* Possibly not, you might be able to jump from 3.5 to 5.8, but unless your Confluence is only using really basic functions, it's unlikely. The route you have here is the recommended one * Yes. But you don't have to actually use them * No. The same licence will work all the way though * No. You're trying to do something…
-
Run a filter that includes them and use that in the gadgets. Some gadgets have hard-coded filters, so you'll want to drop them and use ones that let you choose a filter instead (e.g. assigned to me -> filter gadget)
-
Remove the fields from all the screens except "view issue" (i.e. they should not be in create, edit or transition screens) Set the dates with post-functions on the transitions (from memory, you'll need a plugin to do this, like Jira Misc utilities, but try it in native Jira before going looking for a plugin)
-
Ok, so when you've written it, all you should need to do is use "upload" in the manage-addons section of the admin screens.
-
The only "jira-python add-on" I know of is a library of python functions for helping you code for JIRA. There's nothing to install in JIRA. Could you explain which add-on you are looking at, if I've got the wrong one here?
-
You could take this approach, but surely it would be easier to use a label field?