Difference between revisions of "Template talk:Jira"
Alissa Sabre (talk | contribs) (https vs http) |
Dzonatas Sol (talk | contribs) |
||
Line 12: | Line 12: | ||
-- [[User:Alissa Sabre|Alissa Sabre]] 23:55, 26 October 2007 (PDT) | -- [[User:Alissa Sabre|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? | |||
**** [[User:Dzonatas Sol|Dzonatas Sol]] 07:17, 27 October 2007 (PDT) |
Revision as of 06:17, 27 October 2007
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)