I have a custom field named as workaround in Jira. Whenever I put a mediawiki link into it with the alias it does work for ex: [[Documentation:Product:Manual:TopicName|alias]] is the text in my workaround field. it should get converted to link but its not happening
It sounds like you need to use a URL, not MediaWiki markup. As Tgr says, you shouldn't expect MediaWiki syntax to work in software that isn't MediaWiki. For how to make links in JIRA, take a look at the the JIRA wiki docs.
Related
As per redoc github page, there is an example of real life usage for Rebilly API. I really like its formatting and would like to use as my formatting as well. I have created open api yaml file using redoc but formatting that comes out of box is not that appealing.
Does anyone know how can we get same formatting as Rebilly API?
Rebilly is using a paid version of Redoc. You can test it for free at https://redoc.ly.
for the coloring, I think some basic theming/coloring is still possible in the free version of ReDoc. Try this online theme editor to see what are the available options: https://pointnet.github.io/redoc-editor/#/
I was hopping to have an easy way to customize the display behavior of the Grails fields plugin after reading its docs, but I just realized that it demands an enormous effort as there is no available templates to start from.
I can see the display functionality is hard-coded in FormFieldsTagLib (from methods like renderDefaultInput() ) but I think it is imperative to have the templates themselves (or a way to generate them, somewhat like generating static scaffolding in Grails).
I can see no consistent (and reasonable) way to customize display behaviors for the Grails fields plugin without that. Am I missing something?
Imagine the use case where someone wants to change the boolean default rendering just to display the field label after (and not before) the checkbox, and keep it available to all the boolean fields within its application. Which concerns will he need to handle regarding if the field is required, has errors, prefix and so on? When all he needed was just moving two divs around.
Grails version: 2.5.4, fields-plugin version: 1.5.1
You aren't missing something. You'd have to re-create the existing implementation of each field type rendering in a template for use with the plugin. There isn't a way to generate a file to start with (like scaffolding).
I won't bore you with the historical reason as to why this is the case, but if you do create a set of base templates it would be a good idea to contribute back to the plugin.
I had an issue with the <f:table> tag, and found this post, which led me to find the base or default template inside the plugin repo.
Take a look at
https://github.com/grails3-plugins/fields/tree/master/grails-app/views
That may help you finding some default templates, along with the official doc and this answer on where to put the override.
Hope it helps you.
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.
Is there a way to change the help link in the toolbar dropdown in the new visual editor of MediaWiki?
I tried setting
"visualeditor-help-link":"mw:Help:VisualEditor/User guide/de"
in
"extentsions/VisualEditor/modules/ve-wmf/i18n/de.json"
as proposed here, but then my MediaWiki could not parse the JSON file. My goal is to link to the MediaWiki help page, that can be found here. The normal version:
"visualeditor-help-link":"[https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/de]"
did not work, neither did this:
"[[{{MediaWiki:visualeditor-helppagelink}}|Hilfe]]"
You should never ever change the source code of MediaWiki core or any extension. It makes an upgrade process much more hard and complicated. There are other ways to achieve a high customization of the user interface language :)
For your problem, it should be enough to create the following page in your wiki (like any other page, but you need the editinterface user right, which is assigned to sysops by default):
MediaWiki:visualeditor-help-link
Put the link you want to use into the textarea (without any wikitext, e.g. "Help:VisualEditor" (without any ")) and save the page.
After reloading the VisualEditor (maybe you need to clear your browser's cache using Ctrl + F5) the link should point to the new target you specified in the message above. If you use a message cache, it is maybe needed to rebuilt it.
I've got an article in Main.
I want to link to it from another Web, call it Acme.
I've tried
Main.MyLink
%Main%MyLink
but can't get it to work.
What do I do now?
The general syntax for that is
web.topic
so you should be fine with
Main.MyLink
if you want to link to a topic MyLink in a web named Main. If your web Acme (or your whole wiki) has disabled auto-linking in the preference settings, you need to use the square brackets notation, e.g.
[[Main.MyLink]]
or
[[Main.MyLink][my link]]