I'd like to edit the Affects Version/s field of an issue in Jira, however, the field is not editable. I can see the field, but the None value cannot be changed.
From what I've found, this is commonly caused by the lack of version(s) in the project. There are existing versions in my project (in various states too).
In the Screen schemes menu of the project settings check if the desired field, in this case Affects Version/s, is on the edit issue screen.
If it's absent, add it using the Select Field drop down menu at the bottom. Once the field is present you should be able to edit the field, either from the regular task view or the edit screen.
In JIRA there are three type of screen create, edit and display.
You are able to see the Affects Version/s field of an issue in JIRA but not able to edit it.
You are able to see it because this Affects Version/s field is present is display screen. Just check if it is present on edit screen also.
this kind of problem we face if any field is present is display screen but not in edit screen.
Related
I've had some testers reporting an intermittent issue on a search page that contains a list.
They say when they have been on the page and navigate to a sub page then return that the list is sometimes scrolled all the way to the bottom of the screen.
I've disabled tensile drag on the list, but I wanted to know if there was any other work-around for this issue?
This has nothing to do with tensile drag. When you navigate from one form to another in the old GUI builder the form is re-created from scratch and re-positioned based on the data.
We try to select the previously selected item but if something in the list changed this might trigger issues.
You can override restoreComponentState in the state machine with a blank implementation to see that this is the cause of this behavior. Assuming that it is you can create a special case for the list instance.
I have created a form with 6 sections and configured Cancel, Next, Prev and Submit buttons in properties-local.xml.
It is usually not advisable to allow the end-user to submit the form until they have at least reached the final section. The only way I can see that this may be possible is to use buttons within the form and by checking which section is currently in focus.
I notice that this has been fixed for Orbeon 2016.1 (see Is it possible in orben to hide or disable the "send" button until a form is finished?), but just wondered whether there is a workaround for Orbeon v4.10?
With 2016.1, this requires the following conditions:
Use of the oxf.fr.detail.buttons.inner property.
Use the wizard's validated mode.
The documentation on this was missing. I have just added it. I hope this helps!
I want to make two fields always visible on JIRA screens, but not be required.
That way I don't have to open the edit dialog to add story points, but can add/edit/read stories before they're estimated.
How can I make a non-required field always show in a JIRA screen?
You should go to Admin>issues>Field Configuration section. Once here you have to choose your current Scheme and open it.
You will see a screen with all your fields. There are 3 columns, Field name, Screens, and operations.
Go to the field you want to make visible and optional. Set the screens where you want to have it present (i assume that at least you need to add it on "View issue screen", or the custom name you gave it).
Finally make sure that at Operations column, you have correctly set it for been shown (If it allows you the "Show operation" means that it is hidden, and if it shows you "Hide" operation, means that it is gonna be shown)
On the same Field configuration screen, you can make a field Requiered or optional at operations column
I've got a number of buttons in a view and have assigned a tag number to each for identification in code. I just went back to check one of them, and can't find the field in the Attributes Inspector where I originally assigned the tags. I've tried all my buttons and restarted Xcode, and the result is the same--no tag field.
Here's what my attribute inspector looks like with a (tagged) button selected in the storyboard:
I came upon a recent comment by someone who also couldn't locate the tag field. He also is using Xcode 5.0.2.
Anybody else run into this?
Thanks!
The sections in the attributes inspector can be shown or hidden by clicking on the lines where the words "View", "Control", etc appear. When you rollover the line with these section titles, you'll see the words "show" or "hide" appear on the right edge of the line. Clicking anywhere on the line toggles between the two states.
Where it says view: Move your mouse over to the far right and something should appear that says "Show". Click on it and you'll see the tag identifiers, etc.
I am trying to display items retrieved from an XML DB using xforms:select1 control using appearance=xxforms:tree. The items appear collapsed or expanded automatically and the behaviour is not the same for all the items retrieved. I have the following questions regarding xxforms:tree view:
how to make sure this view shows sub-nodes (those expandable/collapsable using +/- icon) as collapsed or expanded always, irrespective of, for example, the no. of nodes covered by the + icon?
how to render select1 with tree appearance without making any of the items hyperlinks?
how to make sure no item is highlighted/selected by default?
...and although the docs say xxforms:menu is also a possible appearance (URL http://www.orbeon.com/orbeon/doc/reference-xforms-extensions#tree), the details are not available...
About which branches of the tree should be open — By default all the nodes leading to selected nodes are open, this so the selected values are all visible. But you can change this default behavior and specify which nodes should be open using the xxforms:open attribute. For more on this, see the section "Controlling which tree nodes are initially open" on Selection Controls. Note that this feature was added in October 2010, so it is not included in Orbeon Forms 3.8, and until Orbeon Forms 3.9 is released, you'll need to get a nightly build for this.
About using links in the tree — At this point, the nodes you can click on in the select1 appearance="xxforms:tree control are rendered as links, so users know that this is something they can click on to make a selection. I assume that you don't want them to show as links because the tree might be "read-only" in your case (for information only, not to make a selection). This isn' supported at this point. As a workaround, you could use CSS to change the pointer and appearance of links in the tree so to users they don't even notice that this those are links.
About the menu appearance — It works very much like the tree appearance. See for instance this example using the menu.