Template talk:Jira
tweaking to make it more usable
If the string parser functions were installed (it's listed in Jira), you could skip out the alt parameter and expand the abbreviation to the full name.
As it stands I could probably tweak this a bit :-D
SignpostMarv Martin 17:35, 18 January 2007 (PST)
https vs http
The current template uses https: to access to jira.secondlife.com. I think http: is better for this purpose, because (1) http is lightweight over https, and (2) an https: URL is rendered with "Locked" icon that may scare users.
-- Alissa Sabre 23:55, 26 October 2007 (PDT)
Do to the way JIRA keeps session information, we have to use https for it to work throughout JIRA. We could log onto JIRA, and then later use the wikipage to get directly to a jira issue and edit it without the need to relogin. It is a bit of a pain because of the potential lag, but it heals the relogin issue. Normally, users would have raw jira accounts, and the http method would work fine, but the SL users have a special user account that doesn't work currently as a raw jira user account. This template is used heavily for the triage agendas, so we can expect the need to edit without constant a re-login prompt.
How about an optional variable to this template?
- Dzonatas Sol 07:17, 27 October 2007 (PDT)
Link decoration
I would like to add <span class="plainlinks"> to this template in order to make the links look nicer. It would also solve "looks scary for new users" problem, Alissa Sabre referred to in the previous comment.
Objections?
(P.S.: Just partly related, but is there a way to have a link beeing not underlined?)
Greetz, 
Lynch (talk|contribs) 13:26, 11 September 2008 (PDT)
- I have no problem with plainlinks being added, I don't think the underline decoration can be removed. -- Strife (talk|contribs) 09:52, 12 September 2008 (PDT)
Updating the format of this template
As I mentioned on Template:JiraIssue I'm thinking it might be nice if this template could be expanded to be more consistent with Template:Issue to support type, resolution etc, creating plainer links only if those bits of information aren't provided, so we can include as rich or as simple a jira-link as we like.
For example:
{{Jira|VWR-7830|Automatically switch active group on group land|type=nf|resolution=open}}
Would look like:
VWR-7830 [A, C] - Automatically switch active group on group land
Minus all the external/secure link icons of course, not sure how to get rid of those…
-- Haravikk (talk|contribs) 03:40, 21 April 2011 (PDT)
Replacing JiraIssue
Already hinted at this, but we shouldn't really both this template and Template:JiraIssue as they both do almost exactly the same thing. The main difference between the two templates is that any title entered is display in addition to the JIRA issue ID, while this template will only display the title. For compatibility I'd like to propose that if a title is entered then it should be displayed in addition to the JIRA issue ID. However, if the title is entered using the alt variable then it replace the issue ID, this way we should be able to get both behaviours allowing for explicit JIRA links, and inline links from part of a sentence.
For example:
{{Jira|VWR-7830|Automatically change group on group land}}
Would produce:
VWR-7830 - Automatically change group on group land
While the following:
To view my JIRA issue please {{Jira|VWR-7830|alt=Click Here}}!
Would produce:
To view my JIRA issue please click here!
This would ideally be in addition to consolidating this template with Template:Issue, however the alt variable would like override all normal automatic formatting in favour of producing an author-defined link.
-- Haravikk (talk|contribs) 04:32, 24 April 2011 (PDT)
- I like the proposed change in functionality. I'm not sure how prevalent the two usages currently are. Part of making this change is going to require changing all instances of the '2=' syntax into the 'alt=' syntax as to not break content. Considering how heavily this template is used, it is something a bot would need to do.
- As to the merging with Template:Issue, doing so would have huge performance costs.
- Template:Jira - primary function is to provide a deep link into the issue tracker. It requires no format structure, it can be used in the middle of a sentence. It allows for a user to quickly go from an article to an issue.
- Template:Issue - is a row template used for lists of issues. Lists of issues by definition comply to a list format. This template makes converting the issue information into a list row easy (in theory).
- Template:Issues - template used to make transclusion of Template:Issue easier in LSL. Because issues ultimately end up being described in multiple contexts, it can help to store the info in a single stub template. Doing so makes it possible to quickly update all instances.
- Now it would be interesting to have issue information accessible to Jira links (hover over it and it brings up a description). This can be done. If we are going to do this, we may want to create an issue information store template that Issue and Jira can read from. Each level of complexity we add to commonly used templates is going to result in a significant performance cost. It's times like this I wonder why web servers don't use JIT compiling.