JIRA description's editor disappeared - editor

I have a strange issue that I'm unable to resolve in Jira settings or find any information online.
Running JIRA Cloud.
The editor for the Description field is all of a sudden missing editing controls. See attached image. Screenshot is from JIRA that I edited, not from our instance. I feel like we had it couple of weeks ago and I just didn't notice it and all of a sudden it is now GONE.
Any ideas if it's a setting or add-on??
This is our editor:
In addition, the comment renderer used to render #Person links as Person Name blue link, and now it just displays it as [~Person] plain text.

Looks like the description and comment fields on your JIRA are configured with the plain text renderer instead of the wiki renderer.
If you're a jira administrator, you can go to Field Configurations, then click Configure for the Default Field Configuration (or any others you may have). Now look for the description or comment fields and check which renderer is configured for them.
More documentation available here.

Related

How to add hover texts to Vaadin components?

How can I add a hover-text (i.e. a text box containing some explanation or details appearing when I hover with the mouse over a component) to TextFields, Tabs, Links, Labels, etc.
I googled and scanned the "Book of Vaadin" as well as "Building Modern Web Apps ..." books and neither contains any relevant info on hover-texts.
Have I missed something? Or are they known under some different term?
For example you can add a title:
yourComponent.getElement().setAttribute("title", "Your Explanation");
Read more about the title attribute in the docs: https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/title
If the native title attribute is not enough, you can look into add-ons. The Vaadin Directory has a Tooltips4Vaadin, or Tooltip. The second one is CVAL 3.0 licensed, but I believe it should be Apache 2.0. At least the corresponding web component is Apache 2.0.

Jira - attempting to make a field NOT REQUIRED

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.

Cannot update custom field description

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.

Trac to Jira migration: Converting a text in webpage to hyperlink on pageload

We are in a process of migrating trac to jira(defect management tool). I have imported data from Trac to Jira. The changesets that were present in the trac tickets are seen as plain text after importing them to Jira. On verifying the page source, the class name of all such spans is changed as error. Below is part of page source:
<a class="user-hover user-avatar" rel="username1" style="background-image:url(/secure/useravatar?size=small&avatarId=10122);" id="commentauthor_402362_verbose" href="/secure/ViewProfile.jspa?name=username1">username1</a>
added a comment - <span class='commentdate_402362_verbose subText'><span class='date user-tz' title='28/Oct/11 5:53 AM'><time datetime='2011-10-28T05:53+0530'>28/Oct/11 5:53 AM</time></span></span> </div>
<div class="action-body flooded"><p>(In <span class="error">[12345]</span>) refs AGLBD-16096</p>
Here [12345] is my changeset number. What would be the best way for me to make that changeset number appear as hyperlink instead of text. This should also be working with any ticket that a user opens. All the corresponding changeset numbers should be changed to hyperlinks on every page.
This was one of the most valuable things we also needed when importing our trac issue and comment history to JIRA was to preserve the changeset links made via autocommit hooks from subversion commits. We also had multiple repositories enabled in trac which made the link conversion tricky. Unfortunately the JIRA trac import doesn't seem to support any kind of repository changeset link conversion at all, including to Fisheye if you have that imported and enabled already.
Here's the PHP script I ended up writing to patch the sqlite3 trac.db file before import. I've included our user story, some sample SQL commands used for user conversion and our trac.db schema for reference at the bottom of the script for reference. I hope this is useful for others converting from trac to JIRA.
Are this "changeset" equivalent to JIRA's issue key?
If so, the JIRA will change any JIRA issue key to link to issue automatically, if the user that is browsing the issue have right's to display the mention issue.
For example in your jira you have an project TST, with link to browse it: http://jira.example.com/browse/TST . Issue 1 would have link: http://jira.example.com/browse/TST-1
Any occurrence of text "TST-1" in comments, description, JIRA will automatically change to link to issue TST-1 if, and only if user that is reading text TST-1 has enough permission to browse issue TST-1.
You may also need free plugin : application links

Why does my control (component) disappear when I set the 'control name' to "test-controlenummer" in Orbeon Form Builder?

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.

Resources