Susan Hauth [Jira Queen] Community Champion

Yes "Operations" is still valid. One of our mainstay well used roles and I just double checked in case the upgrade did anything to it, but looks the same.

2015-07-02 18:03:18,860 http-bio-443-exec-1 WARN shauth 1083x1212x3 162b5os 10.9.30.109 /secure/CreateIssueDetails.jspa [onresolve.scriptrunner.runner.ScriptRunnerImpl] Add a script root for this path: D:\Program Files\Atlassian\JIRA\atlassian-jira\WEB-INF\lib\CalculateDueDate.groovy 2015-07-02 18:03:19,691…

It's not the "Summary" tab, it's the original "Issues" tab which is missing and really hurting. So making the Summary page default is fine, but it's really the original "Issues" tab that we can't do without.

Thanks! I have disabled and am now running a compare. Where is "Labels"? We depend pretty heavily on that one. Agile is gone and so is "Popular Issues". I understand Agile, but not "Popular Issues" and "Labels". I have sent in the very scathing feedback, but without "labels" I still may not be able to move to JIRA 6.4.…

Thanks...I'm on it...watch out for some scathing feedback on the Project summary

I did put If comment is internal on the IF statement. But I'm looking for automation if someone does comment from outside of Service desk in the JIRA interface? 

And they're back!! 3 more rank fields showed up today. I think it must be related to when we moved some issues up the queue in Agile.

I have deleted all those rank fields and will monitor to see if they reoccur. Thanks

Yes there is a long list of those Rank fields when I'm in the configuration for Agile. I would need to ask our system admin re the log file, but I thought I would start here. It is odd, but I may try deleting them and see what happens. Hopefully I won't have the user community up in arms if the priority list goes awry.

Hi, We have the same issue. I'm going to look into Buzz, but we need beyond the Phone Number. Our users want to be able to see the Client, Region, phone number and a flag when they hover over a User. I have gotten around this by using post-functions to copy the User Properties into custom fields onto each issue that a…

Hi, Thanks much for the script but a little too advanced for our shop. I've gone back to my team and said "make it smaller"!!

Jamie, I seriously don't know what I would do without you!!! Thanks...it worked...

Thanks!!! A little trick I did not know. 

Thanks!!! Duh on my part... :-)

That's strange. We just upgrade to JIRA 7.3.2 and Service Desk 3.3.2. WOrked fine

Hi, Had the same problem and found out it's because this seems to only work when I'm logged into IE in JIRA. S

Hi, I do that quite frequently in my JIRA projects. I set the Issue Created notification to notify the component lead so they know the issue has been created, but I set the assignee in the workflow to something else, often unassigned. Just do it after the "Issue Created" step in the post workflow of the Create.…

Hi, Under JIRA 4.1.1, I was able to import the custom fields without having to make them global. I'm importing about 10-15 custom fields, this is a huge pain to make them global. I'm not sure how this is an improvement?? I am importing project by project. Of course it would really help if Step 6 was there, the one that…

I have voted and am watching this issue. A workaround does exist (bracket, squiggle, username, close bracket)

Here's what it looks like...And it's not Yoda who's so small...LOL

Thanks Chris, I have voted for it!

@Chris Fuller , So was there an improvement request raised for making the creator field "orderable"? If so, I would like to vote/watch if not I would like to raise one. Point me in the direction. Just saying this is kind of half-assed to add this field as only navigable.

That's strange, because I'm a JIRA Admin (jira-adminstrators, jira-sysadmin, jira-developers) and I'm currently able to click on an Avatar in another User's profile and update it no problem. Standard jira-users do not have that ability.

We are trying to differentiate between the "tempo log work" and the Jira "log work". As they give different features.

Hi, We are looking for this feature as well. I see that this question never received any answers? Or did you find a way to manage this?

IMHO I think they broke something in JIRA 6.4.

I do have conditions on the transitions and properties on that step. The problem was that prior to JIRA 6.4.7 I was able to use a workflow transition to open up the attachments,allow an attachment and close. And it worked fine. Now it doesn't and I did not make any changes to this workflow post upgrade.

But I don't want it in the step property. Because I don't want these fields to be editable except under certain conditions (parent statuses) and only by the reporter.

See below for the transition property. I think I found a workaround. I changed the workflow to go back to Open and then fast track back to close. So while it's "open" I can attach a file and then the post workflow transition sends it to Close. It's just so strange that I can edit fields using a workflow transition while…

Transition Property.PNG