Drop By!

In Jira there is a fixed role “project lead” for each single project which is assigned in the projects configuration. The only default use of this role is as the default assigne of created issues. The problem here is that you can’t change this behaviour (see http://jira.atlassian.com/browse/JRA-3523).

So if you assign “project lead” to the administrative project lead, the mailbox of this person will be filled up with messages on issue creation. This might not be exactly what you wanted.

What possibilities are there to avoid such a problem? (Some only for Jira Enterprise).

1. Using the role “project lead” as a proxy between customers and project team members. In this case don’t use the role “project lead” in your permission scheme, define your own role like “project manager” or similiar and use this instead. And:
   1. Assign “project lead” to a moderator or support team member.
   2. Assign “project lead” to a dummy user with a catch-all IMAP mailbox.
2. Allow unassigned issues: Check admin -> global-settings for “allow unassigned issues” and set this in the project configuration as default
3. You can configure a different default assignee for each component of a project. See http://www.atlassian.com/software/jira/docs/latest/component_management.html
4. Edit you current Notification Scheme and remove Current Assignee from Notification on Issue Created.

In der deutschen Jira-Version wird das Datumsformat unter Administration – Globale Einstellungen Gestaltung eingestellt.
Hier ist ein Beispiel:

Datums-/Zeitformate
Format Beispiel
Zeitformat HH:mm 22:28
Datumsformat EEEE HH:mm Freitag 22:28
Vollständiges Datums-/Zeitformat dd. MMM yyyy HH:mm 21. Nov 2008 22:28
Format Tag/Monat/Jahr dd. MMM yyyy 21. Nov 2008
Format Datumsauswahl (Format javascript) dd. MMM yyyy (%e. %b %Y) 21. Nov 2008
Format Datums-/Zeitauswahl (Format javascript) dd. MMM yyyy HH:mm (%e. %b %Y %H:%M) 21. Nov 2008 22:28

Dabei muss man das Format für die Auswahl in Formularfeldern per JavaScript in einer externen Konfigurationsdatei einstellen:
WEB-INF/classes/jira-application.properties

Ein Beispiel:
# These two properties need to match for the datepicker to perform correctly
# The first date is in Java format
# (http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html).
# The second in unix format (see the FORMAT section of http://unixhelp.ed.ac.uk/CGI/man-cgi\
?date)
# Please note that the following options are not recognised: %c %D %E, %F, %G, %g, %h %r %R\
%T %x %X %z %Z - _ ^ #
# After editing ensure the date picker creates valid dates, we also recommend you make this\
format the same as Day/Month/Year Format
# in the administration section of JIRA
jira.date.picker.java.format = dd. MMM yyyy
jira.date.picker.javascript.format = %e. %b %Y

# These two properties need to match for the datetime picker to perform correctly
# The first date is in Java format
# (http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html).
# The second in unix format (see the FORMAT section of http://unixhelp.ed.ac.uk/CGI/man-cgi\
?date)
# Please note that the following options are not recognised: %c %D %E, %F, %G, %g, %h %r %R\
%T %x %X %z %Z - _ ^ #
# After editing ensure the date time custom field picker creates valid dates
jira.date.time.picker.java.format = dd. MMM yyyy HH:mm
jira.date.time.picker.javascript.format = %e. %b %Y %H:%M

Here a very simple init script tested on Suse SLES 10. An other good way to create one is looking at the init-Script for tomcat or using just it and installing Jira as WAR into tomcat.

#!/bin/bash
# Jira startup script
# install:
# copy to /etc/init.d/jirad
# ln -s /etc/init.d/jirad /sbin/rcmy-jirad
# insserv /etc/init.d/jirad
 
### BEGIN INIT INFO
# Provides:          jirad
# Required-Start:    $local_fs $network
# Required-Stop:
# Default-Start:     3 5
# Default-Stop:      0 1 2 6
# Short-Description: Starts Jira server
# Description:       Starts Jira Issue Tracking
### END INIT INFO
# Based on script at  http://confluence.atlassian.com/pages/viewpage.action?pageId=183148
 
RUN_AS_USER=jico
CATALINA_HOME=/opt/jira
 
start() {
        echo "Starting Jira: "
        if [ "x$USER" != "x$RUN_AS_USER" ]; then
          su - $RUN_AS_USER -c "$CATALINA_HOME/bin/startup.sh"
        else
          $CATALINA_HOME/bin/startup.sh
        fi
        echo "done."
}
stop() {
        echo "Shutting down Confluence: "
        if [ "x$USER" != "x$RUN_AS_USER" ]; then
          su - $RUN_AS_USER -c "$CATALINA_HOME/bin/shutdown.sh"
        else
          $CATALINA_HOME/bin/shutdown.sh
        fi
        echo "done."
}
 
case "$1" in
  start)
        start
        ;;
  stop)
        stop
        ;;
  restart)
        stop
        sleep 10
        #echo "Hard killing any remaining threads.."
        #kill -9 `cat $CATALINA_HOME/work/catalina.pid`
        start
        ;;
  *)
        echo "Usage: $0 {start|stop|restart}"
esac
 
exit 0

This is an addition to my post Convenient SSH on Linux cause I was suprised finding that KDE is run from ssh-agent per default.

# ps aux | grep ssh-agent
userx 6784 0.0 0.0 4480 816 ? Ss 19:02 0:00 /usr/bin/ssh-agent /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/userx/.gnupg/gpg-agent-info-myhome /usr/bin/startkde

So, first, how can you disable this?

In /etc/X11/Xsession.options :
# cat /etc/X11/Xsession.options
# See Xsession.options(5) for an explanation of the available options.
allow-failsafe
allow-user-resources
allow-user-xsession
use-ssh-agent
use-session-dbus
you can disable use-ssh-agent. This option will be used by
/etc/X11/Xsession.d/90x11-common_ssh-agent
see there for details.

If you want to use the running ssh-agent you can add your keys on startup by putting this script to .kde/Autostart
#!/bin/sh
# set SSH_ASKPASS if not set elsewhere
# export SSH_ASKPASS=/usr/bin/ssh-askpass
for f in /home/userx/.ssh/mykeys/*_dsa ; do ssh-add $f </dev/null ; done ;

Also check the related ubuntu bugs

After spending a day and a night I have got this working. Not perfectly as restarting Xserver by CTRL+ATL+BACKSPACE would show a scrumbled screen (see below for a fix).
This is the hardware configuration I tried to get working:
The Laptop “Dell Latitude D810″ ist connected to a docking station “D/Port Advanced Port Replicator”, the external monitor is connected to the DVI-D Port of the docking station. I wanted a big desktop stretched over both monitors, laptop and external, that makes sense cause the laptop can be fixed in a upright position by the D/View computer stand, the resolution of both monitors is 1680×1050.

The main steps were:

1. Updating the fresh installed system.
2. Removing the xorg-driver-fglrx driver package if installed.
3. Downloading the latest ati fglrx driver from http://ati.amd.com/support/drivers/linux/linux-radeon.html and installing them by just running the downloaded ati-driver-installer-8-11-x86.x86_64.run as root.
4. Reading Unofficial Ati Linux Driver Wiki
5. Following descriptions in Dual Monitor Support With Binary, ATI-Only Big-Desktop
6. Running aticonfig according to the descriptions:
   root@myhome:# aticonfig --initial --overlay-type=Xv
root@myhome:# aticonfig --desktop-setup=horizontal --sync-vsync=on --add-pairmode=Width0xHeight0+Width1xHeight1
7. Tuning my xorg.conf by adding some options to the device section.

To make this descriptions complete here is my xorg.conf :
# xorg.conf (X.Org X Window System server configuration file)

Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

First I could fix the freezing of X on logout by disabling acpi. But then I found at Wiki Troubleshooting some hints and had success with:
File: /etc/kde3/kdm/kdmrc
TerminateServer=true
didn’t work alone. Added
sudo /usr/sbin/update-rc.d -f atieventsd remove
with success even with acpi enabled.

Grub menu disabling acpi:

# set this in /boot/grub/menu.lst
title Ubuntu 8.04.1, kernel 2.6.24-21-generic ACPI=off
root (hd0,5)
kernel /boot/vmlinuz-2.6.24-21-generic root=UUID=45c3fc6b-bbcb-4320-8470-9228582f3115 ro quiet pci=noacpi acpi=off
initrd /boot/initrd.img-2.6.24-21-generic


Say you create XHTML from XML using XSLT transformation (like me from Docbook to XHTML chunks using Docbook XSLT Stylesheets ) and you want to include some Javascript in the XHTML output.

If you serve your XHTML pages with mime-type: application/xhtml+xml rather then text/html , you will have to take care of xml-relevant characters within the script code (see Javascript and XHTML for a short explanation):

<script type="text/javascript">
/* <![CDATA[ */
// content of your Javascript goes here
/* ]]> */
 
or 
 
<script type="text/javascript">
// <![CDATA[ 
 content of your Javascript goes here
//]]>
</script>

Generating this output with xslt can be a little bit tricky. My solution (probably better exist) uses a trick shown in http://www.w3.org/TR/xslt#section-XML-Output-Method:

... xslt code ...
<script type="text/javascript">
	<xsl:text disable-output-escaping="yes">
	<![CDATA[//<![]]><![CDATA[CDATA[]]>
//javascript
	<![CDATA[//]]><![CDATA[]]]]><![CDATA[>]]>
        </xsl:text>
</script>
... xslt code