JIRA Configuration Query

[VenugopalY]

I have some questions.

1. How to get email alerts for a failed logins?

2. If user files ticket with improper details through email system. where do tickets go that have no project keyword? how to handle those tickets? Can we revert back to user about right usage model through automated email. For case history please see JSP-146131

3. How to configure Escalate issue like seen in your JIRA support system.

4. Can I have a sample JELLY scripts for

a. Waiting on Reporter, trigger email for every 2 days to remind user.

b. Ticket pending for long time trigger email notification for members/watches for that ticket.

c. On resolution provided and ticket is inactive state for 10 days etc… Auto close ticket

d. Customized reports email notification. Like All Issues In-Progress. Un-Resolved, status tickets. Etc…

5. Any option to export charts to PDF or PPT?

6. Support Rich Text under Description/comments section?

7. Can the new comments be added to the top of list rather than the bottom? New comments should show up on TOP under comments section.

8. We are looking an option.

a. When user try to create issue it should prompt for Case Record Type. Like options below

i. CAD

ii. Customer

iii. Internal

b. When user select CAD Record type he can able to create issue related to projects under this with customized workflow.

c. Like that for Customer and Internal. Each case record type has own projects and related workflow.

Please let me know if you have any questions.

Y.VENUGOPAL | SMTS - CAD Engineer | Rambus Chip Technologies (I) Pvt Ltd | 12th Floor, Tower C & D, IBC Knowledge Park | Bangalore 560029

+ 91 80 4196 6182 | + 91 7760 9988 19

[Mizan · Accepted solution]

3. How to configure Escalate issue like seen in your JIRA support system.

>> A good way to do this is by writing a jelly or groovy (using script runner plugin) service whih will escalate issues based on some criterias

5. Any option to export charts to PDF or PPT?

>> https://marketplace.atlassian.com/plugins/com.xpandit.plugins.jiraxporter

[KhongMingA]

3. For the JIRA support system escalation, perhaps you can have a look on this:-

- https://confluence.atlassian.com/display/JIRA/Automatic+Escalation+of+issues

- https://confluence.atlassian.com/display/JIRA/JIRA+as+a+Support+System#JIRAasaSupportSystem-EscalationandSLA

You can consider plugin to help you to achieve this requirement:

- SLAdiator - service level agreement real-time monitor for JIRA.
- Vertygo's SLA plugin in the Atlassian Marketplace

Hope it helps
KM

[Nic Brough -Adaptavist-]

1. Code changes
2. You set a default project
3. Google "Jira Jelly escalate"
4. See 3 and modify that to suit
5. Not really, but some people have had success with printing from browsers
6. Look in docs for "wiki markup"
7. Yes, it's a setting
8. Have different fields and workflow by issue type (workflow schemes, field configurations and screen schemes)

Most of these are in the documentation. I know there's a lot to read, but barring q1 and q5 they're all in there.

[KhongMingA]

For the Jelly Script, it is impossible to trigget the notifications.

There is few sample jelly script in the documentation that you might want to have a look.

• https://confluence.atlassian.com/display/JIRA/Jelly+Tags#JellyTags-Samplescripts
• https://confluence.atlassian.com/display/JIRA/Jelly+Escalation
  

Hope it helps
Merry X'mas

KM

[tousifs]

4) https://confluence.atlassian.com/display/JIRA/Configuring+Email+Notifications

or we can write the customized listener to work according to our requirement.

1) for failed logon we can make use of listeners for failed logon events.

https://confluence.atlassian.com/display/JIRA/Listeners

[Andy Brook [Plugin People]]

Hopefuly this is constructive; consider breaking up your 8 completely differnet questions into separate questions. By doing this you will increase the chances that someone will spend their time (a) reading and (b) answering them. Remember Karma is allocated to correct answers, how is anyone really going to be able to answer ALL of your questions/points.