Comments
-
Look at the field configuration scheme. At the very least, you'll need to create a new "field configuration", one which says "component = mandatory". You then create a "field configuration scheme" which says "for all issue types, use my new field configuration". Then change project "Test 2" so that it uses your new scheme.…
-
Only if the add-on supports its own licence scheme that can do this. I'm only aware of a couple that do it, and they're not JIRA add-ons.
-
I was going to point you at the config file, but it's moved between versions. Which version of Confluence are you on? (It's similar to dbconfig.xml in Jira, but depends on the version). (In the long run, I'd also mutter about using names instead of IP addresses, but that's not really the short-term answer you need)
-
There are no "revision" tracks. Issues are not static documents with clear "edit 1, edit 2, edit 3..." rules. You need to define *exactly* what you need to think of as a revision. Yes, we can probably agree that updates to the description, summary, due date, etc are probably revisions, but comments representing a…
-
Oh, I also left out the standard advice. Do not waste your time on this. The changes Atlassian made have been made for a reason, which I would say is either "users preferred this view" or "large pages were leading to complaints of slowness, so we broke them up to get a good response back for the users" (There may be other…
-
Check the url - I think it will be something like http://myserver/jira/someotherstuff/projectList.jspa?page=4 The bit you are interested in is the projectList.jspa - that is a generated jsp file which your browser is rendering after the server has built it. It is generated by a file in the installation called…
-
Well, you might be able to get away with just editing the distributed files, rather than what I think of as "source code", but it's still hacking the distributed code. (To my mind "source code" means "blocks of text that have to be compiled into stuff that runs". In this case, you might get away with hacking a .vm or .jsp…
-
You'll need to hack the core code that provides this view to switch it to another format.
-
I think the error message is clear - it's not compatible with your version of Confluence. All you can do is ask the vendor to build a new compatible version.
-
Read the history tab on the issue
-
It is possible, but to use the importer that makes it easy, you need to point it at the Mantis system you want to import from.
-
I don't think it's obvious. The docs don't explicitly say it
-
The licence keys have no effect on your data, they only affect functionality (and that's limited to stuff like "can't log in", "can't add new users", "can't edit stuff" and "you're an admin, here's a reminder that your licence is dead"). Running with a developer or evaluation licence will work fine, and then when you get…
-
Duplicate of https://answers.atlassian.com/questions/22643810
-
See https://jira.atlassian.com/browse/JRA-3821 for the improvement request. Only 8 years old and at the top of the request list.
-
We need a bit more to go on!
-
So, the same principle of a missing field, just wasn't the usual culprit field.
-
No need to apologise! There should be a logs directory under <your jira home>. If you don't know where your jira home directory is, then look at Admin -> System Information, that will give you the full path on the server. The file to look for is atlassian-jira.log (there may be others in that directory that could tell you…
-
No, don't change it.My logic here is a bit twisted, but I'll try to explain. The error you are getting is usually, but not always, down to some form of validation in the project preventing the issue being created. Most of the time, people tend to use the default settings for Service Desk projects, which work fine, but can…
-
Sorry, I was wrong. I've just spent weeks with JIRA Admins who know where almost everything is, so I don't have to explain too often, and I'm using the wrong phrases."Allow unassigned issues" is in "General Configuration", not permissions where I mislead you.I'd also still check the log file for errors with the same…
-
Ok, I know this one. Mostly. This is almost certainly down to permissions, and it's almost always that the default assignee for the issue is not an assignable user. Check the settings for the project, the "allow unassigned users" global flag (don't change it, just confirm that it is off), and look in the log file - if it…
-
Not really, not without knowing what the error is. What does the user see? Also, if that's not a lot of detail, what does the log say when they try the creation?
-
No, you need to edit all the issues if you're determined to remove a user, including deleting all the user's comments. Most of us don't bother - the standard procedure is to remove the user from all groups and roles, which means they won't be assignable, and won't take up any licence seats, but you'll preserve their…
-
Take a closer look at the field configuration, as above.
-
In your screenshot, look at "environment" - you see where it has the "required" link? That's a toggle. If you click it, you'll come back to the same place, but it will not show "optional" (and your users will have to fill in environment) Some fields cannot be made mandatory or optional - you can see the Epic fields in…
-
CLick in the same place - it's an on/off toggle.
-
I don't think this is allowed at all, but you could raise it with support to see if they'll grant you a read-only account.
-
What does the log file say when you try to do an update? (Please note, we're not support, we're a community of end-users. We will try to help, but it's not formal. If you need formal help, visit https://support.atlassian.com )
-
Yup, exactly what I was thinking - I've had to replace a handful of velocity fields with assorted tricks to make up for the removal of Veloocity fields from the Toolkit plugin
-
I think you've put your text in a "view" field which will NOT be processed on Create/Edit screens. Try putting your text in a "Message Custom Field (for edit)" instead. If that doesn't help, then simplify - try plain text instead of html and see what that gives you.