Create Change Request in JIRA

If a question needs a short (or longer..) answer, anyone can send an email to kentucky@semcon.com, but if the question is about changing anything in the system, a change request must be created in JIRA. Contact your SuperUser for the implementation you are working with for this.

Each Implementation of Kentucky (so far over 20) has one person acting as SuperUser which besides holding major responsibility for the implementation, also is the one who creates change requests in JIRA, the event system Semcon uses for Kentucky. He or she has an account in JIRA and starts by login to JIRA from the following address ;

http://idev.semcon.se/jira/

Normal Semcon "s-number" and ordinary network password is used as login values.

  1. Go to correct project / planning board

    After the login, click on "Agile" in top of the window which comes up and select wanted planning board. The screen should look similar to below image (this example comes from the Consilium implementation).

  2. Create the request

    After that click on the "Create" button to the right of "Agile". The screen should look similar to below image. Observe! Try to write your text in english, again not always the same personal who reads your text.

    Project : should already be set, no need to change.

    Issue type : Select type of change (bug, new feature, task or improvement)

    Summary : Short summary title describing the change.

    Priority : Set wanted priority. Note, this setting only implies to current implementation, not all.

    description : Write a more fully description on the wanted change plus an example which narrows down the change. Typical a topic-number, folder-id or other descriptive text. Attachments like images or office documents like Excel or Word could also be added.

    When done press the "Create" button.

  3. After the create form has been filled in, an email copy of the request will be sent to both the SuperUser and the kentucky support personal. Support will evaluate if the change could and should be done and moves the request from the "Backlog" column to "For Analyze". In either case, an email is always sent to SuperUser reporting latest change to the issue. If information is missing or incomplete, comments are added to the request, so it is important for the SuperUser to keep checking email replies from JIRA so delays can be avoided. Avoid sending emails, input further comments directly in the change request instead and all involved will get an email about your latest comment. Reason is that it is not always same personal doing each step, plus that it is important to keep all info in one place for future changes related to this first change.