LarryBrock Community Champion

Hi @Nicolas FILIPPI, Thats great news! Could you click the check mark next to my answer to mark the question resolved? Doing so makes it easier for others to find when searching. Thanks!

This never fails (and yes, safe for work but might lower your volume): https://youtu.be/hXlY9pZUknY

I'm right there with you Max! 

Could the same user be listed as the reporter, a participant, and/or a watcher? This could potentially generate multiple emails. If this solves the problem, please do "accept" this answer so others can benefit. Cheers, ~~Larry Brock

Hello @Jonnada Kiran, It's been a while since I've written irules for F5 but it appears your logic for "/rest" sends it to nodes 1-4 when I'm guessing you want it to go to node 5. If so, maybe this will work: rule divertingtraffic{ when HTTP_REQUEST { if { [HTTP::host] equals"jira.charter.com"} { if { [HTTP::uri] contains…

Hello @Nicolas FILIPPI, The only way I can think to do this is to use security levels with a rule allowing only a limited number of people to see the issue. One of those allowed can be set to "assignee" so as soon as the agent is assigned the issue, it becomes visible to them. Hope this does the trick for you, ~~Larry Brock

Hi @Tim Van Kerckhove, Please do add the name of the add-on that appeared to cause the issue. Many others will benefit from your experience. Thanks!

Hello @Sarah Martin! Could you post the URL for the instructions you followed? What versions of Jira/Confluence are you running? I believe that if the Confluence requirements page has an epic link on it, any issues created from a table on the requirements page can or will use that epic. What I can't discern from your…

Hi @Marc Moroz As far as I know, there are no macros for Info, Tip, Note, and Warning like there are for Task Report. One might be able to do something similar with excerpts and labels but I suspect that would not be a trivial amount of work. --Larry Brock

Hello @Marcin Jira assigns colors to epics so they are easily recognizable. One place the colors can be selected is from a palate on the dropdown menu for the epic on the Backlog page for the project. Click the work EPICS if it's verticle instead of horizontal to make the list visible. (Similar to how VERSIONS is closed…

Thanks Nic and you're right that one cannot change the field, only move the data to a new one (then remove the old one if appropriate). Laura - Do these posting answer your question? If so, please click the "Accept as Solution" button so others know it does. Thanks!

My apologies Yannick - this works for internal Jira users but not for external JSD customers. The only solution for that is to use the add-on @Susan Hauth _Jira Queen_ suggested. --Larry

Found this answer in a similar question. It wasn't the Accepted answer but it doesn't require any Add-on and I believe it's applicable here: This method can be used without any add-ons or plugins tested on JIRA OnDemand (Cloud). Also note you can probably use excel format for import but I prefer CSV. I tested this first by…

One effective strategy I've used is to create a parent page for each reoccurring meeting with some descriptive text about the meetings purpose and expected results plus three macros. The first was a "create from template" macro-generated button that launched a new Meeting Notes page under that parent. The second one listed…

If the notes are organized in a tree, or with a common label, one can use the "Task Report" macro to capture and display tasks on the current page. There are switches available in the macro to further refine the search based on labels, assignee, created by, task status, etc. Where I previously worked, we had a parent page…

Here's the stanza from my apache config: # Keep everything on the right track by redirecting all traffic to the fqdn <VirtualHost *:80> ServerName jira ServerAlias my-jira Redirect permanent / http://jira.company.com </VirtualHost>

What do the permissions say if you click the lock icon? Is this a space admin or a confluence admin account?

Hi Yannick, A workaround, until the improvement @Susan Hauth _Jira Queen_ mentioned is implemented, might be to include the field on the Request but hide it and auto-fill it with a place-holder value like "change-me" or "triage". This way, the field is part of the issue and visibile after creation but not visible during.…

Wow, that's some bling ... er flair (both individually and combined)!! That's gonna be tough to compete against but "challenge accepted". :-)

Excellent! This was where I was headed but wanted to confirm with your specific version of JSD. Then I got ambushed by "real work" and didn't get to follow up until now. Cheers!

Hi Danilo, What version of JIRA ServiceDesk are you using? It is possible that permissions are causing the visibility of the "Close" button to be different for you and the user or one user to another. --Larry Brock

For "real, Atlassian support to get this resolved instead of Comunity Based support?", you may want to visit https://support.atlassian.com/contact/#/

Hello Henrik, I set up a "Stop" transition that moves the issue from "In-Progress" back to "Ready" which is the status we use for submissions that have been triaged. This seemed to compliment the "Start" transition quite well and has been well adopted. The post-transition of "Stop" records the time the issue was "In…

Suha, IIRC, the permission can be granted to a role, a group, or an individual user.

We have used the "Create on Transition" add-on in a number of workflows with great success. Nic is also right - "Script Runner" for JIRA can do the job well also.

Hi Jeff, You might get more response if you make this a stand-alone question instead of an answer to someone elses question. Making it a stand-alone question will make it visible in searches for calendar questions.

Could one do that easily by just flagging the content as spam?

Many new and experienced JIRA Administrators find the JIRA Admin Strategy Workbook to be quite helpful. It's written by Rachel Wright, a well-seasoned JIRA adminstrator (who is currenty touring the country speaking to user group meetings and conferences) for other JIRA adminstrators and is full of "from the trenches"…

Oops, didn't mean to reply on a thread - see my "answer".