I added a custom field to my Mantis BT installation. However I can't figure out how to get it to show up on the Enter Report Details page or the edit details page. (I was able to figure out how to customize the View Issues page and some other places.)
What do I need to do to be able to edit instances of the new field. Along the same lines, there are existing fields which I would like to hide in the editing views.
You can do this from the Manage Custom Fields page. Click on the custom field and you should see the following options:
Display When Reporting Issues
Display When Updating Issues
Display When Resolving Issues
Display When Closing Issues
Required On Report
Required On Update
Required On Resolve
Required On Close
With these options you could control where to display the custom fields.
Related
I have a project which is using Umbraco v7.7.9 installed with nuget.
I was wondering if it is possible to change the buttons displayed in the sidebar section when a user selects to preview a content node. Particularly I want to remove the option that allows the user to close the preview.
The reason I want to hide this option is because some of the content the backoffice users will be previewing will not actually be published yet so clicking the close preview button causes an error.
I first asked this question on the Umbraco forums but haven't received a response yet, here is the link to the question: https://our.umbraco.org/forum/extending-umbraco-and-using-the-api/90878-editing-preview-window-sidebar-options
Thank you in advance.
Currently no - it would not be possible without doing hacks in the Core that would be overwritten when you upgrade your site (unless you manually merge your changes in when updating).
If you however don't mind doing that - the file used for the preview function is /umbraco/preview/index.html. You should look for the element with an exitPreview() click handler attached to it.
In later versions (7.10+) this modification will have to be done in /umbraco/Views/Preview/Index.cshtml instead, as these static files will be changed to MVC actions.
Is it possible to customize the "Create Issue" from per role?
In fact, I simply want to show a reduced set of fields for reporters/users to not overwhelm them and prevent incorrect filling out of unnecessary fields.
Developers should see all fields so that they can provide all necessary/internal details.
In JIRA you can install the plugin "Script Runner" which contains a module called "Behaviours". This module allows you to define fields which should be visible for a specific gruoup or not.
In JIRA we don't have ability to customise this without install plug-ins and edit templates on server-side. Maybe most easy way this is create two different screens in issue screen scheme. First screen(simply) for issue create and second screen(full view) for edit&view.
https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/server/overview
We have an existing text field 'Defect Found Version' (DFV) and a new Field I have created 'Defect Found Version Picker'
I have made the Picker mandatory & that works fine, listing all the cersions on the project.
The DFV field is set to 'Optional' on the right hand side of the Configure Field layout page, however next to the name on the left there is the text REQUIRED & I can not see how to disable this.
Even if I remove this field from all screens I get an error when I create a bug saying that DFV is required.
Any thoughts please ?
Look at the Field Configuration Scheme used by the JIRA project. Then look at the field configuration used for that issue type. That's where it is being made required. Unless it's because of the JIRA Behaviour plugin, so check if that is active
Do you have take a look on your Workflow validator ?
Sometimes, it's required on your workflow, and not on your screen.
I'm using JIRA 4.1.2. I have a page layout created using Jelly, but now that the app is in production I need to manually change a field description (can't run the script again).
The documentation says to go to Field Configurations -> Configure -> Edit, enter the text and hit update. I do that but nothing changes. HOWEVER, for a field that was created outside of Jelly, using the standard JIRA UI, an update works.
What gives? None of my jelly-created fields will update.
Thanks for any help!
Check which field configuration is being used for a specific issue.
I'm building a form in the Orbeon Form Builder. The simplest way to recreate this problem is as follows:
Put a control on the form.
Give it any label, it does not matter.
Go to 'control details'.
Change the 'Control Name' to 'test-controlenummer'.
Confirm with the 'apply' button.
See the control itself disappear
Notice that the question mark of the help feature does not disappear, nor do the delete and validation options once you hover over the formerly-visible-component. The grid cell also acts as if it was occupied. The control simply does not show and some of the changes to the name and/or validation options result in XPath expression errors.
I have taken a quick look at the underlying xml code, however at first glance I did not find anything out of the ordinary.
It disappears because of a bug in Orbeon Forms 3.9 when control names contain a dash. Like you said, there is nothing wrong with the markup Form Builder generates, but it then incorrectly just doesn't expect a dash to be present in the control name.
This bug has been fixed in the latest code, so it won't be present in the next release.
If you are using Orbeon Forms PE, I recommend you contact Orbeon to see if you can get a patch for this (either through Basecamp if you already have a support account setup, or by email, info AT orbeon.com).
If you are using Orbeon Forms CE, for now, you can work around this issue by avoiding dashes in the names of your controls.