Matt Doar_tzgiej Community Champion

Why do you want to do that? What is your goal? Perhaps you can use a component and an issue edited event

I think I'd use the nFeed plugin

Very useful, thank you

Nice. Now I think it's all javascript calls pulling the groups and users from the server.

When you add a project role to a notification scheme for the issue created events, and a newbie project admin then adds jira-users to the project role. Which means that everyone in the company gets email when an issue is created in that project. This spammed 15,000 users including the CEO of a well-known company a few…

ONG: Abbreviation in French, Italian, Spanish, Romanian and Portuguese for non-governmental organization (NGO in English) Perhaps: project = cb and "date of birth" >= startOfMonth() and "date of birth" < endOfMonth(1)

Posted on behalf of a friend, of course :)

There is the classic unexpected space at the command line. Instead of typing rm -rf /foo/bar/baz to delete just the baz directory, you type rm -rf / foo/bar/baz with a space after the first slash. And destroy the whole machine! This is why I type ls / foo/bar/baz first to check for errors, then up arrow and edit the line…

CSV imports sure can make a big mess. That's why I always want to do them in staging first.

Yup. Done that. The missing where clause is an SQL pit trap

Thanks, useful pointer. Shame the new column hurt performance! I've never really accepted the official Atlassian stance of not using the database, since so many support cases are fixed by changing the database :)

You'd need to use Chrome and Inspect the select element. Find the Javascript that sets the width for that element and override it. Sorry not to be more specific but the exact code changes with Jira instances. If you give the priority options a description value when they are defined, you might get lucky in newer versions…

The info is in issue.fields.parent in issues of type sub-issue, such as Sub-task jql = "project = MYPROJ and type = Sub-task" issues = jira.search_issues(jql) log.info("Found first %s subtasks" % len(issues)) for issue in issues: print "Parent %s of subtask %s" % (issue.fields.parent, issue.key)

Sometimes, "assigned to everyone" translates as "assigned to no one." Very true!

Oh yes, that really messes up Jira reporting!

It's true! I was writing my first O'Reilly book in 2004 and I had some questions about this new Jira tool. So I wrote to support@atlassian.com and got a rather knowledgable answer back from Mike. And Jira got a section in the book, the first print reference as far as I know.

Nice!

Yup. Looks like someone missed a step in the release process! 

Ah, I think you want to disable the issue type, so no new ones can be created, but old ones continue to exist. There's a long-standing request for that at https://jira.atlassian.com/browse/JRASERVER-16683 https://community.atlassian.com/t5/Jira-questions/disable-issue-type-creation-temporarily/qaq-p/143446 is an old way…

No, because every issue always has to have an issue type. But you can bulk change issues to a new issue type and then remove the old issue type. 

How well does searching for labels with non-breaking spaces work?

Name the request type "Feature Request (Internal)" and add a description why. 

I don't think that's possible without some serious js hacking somewhere. In Jira Server this might let you do that: https://scriptrunner.adaptavist.com/latest/jira/CustomisingUI.html

Confirmed, it's missing. I think it is supposed to refer to https://confluence.atlassian.com/display/ACCESSIBILITY/JIRA+VPAT+for+Section+508+compliance Worth telling Atlassian Support about this I think 

I'm guessing you mean https://www.atlassian.com/accessibility Which is the anchor that is not working?

Thanks, now I see it under License at https://marketplace.atlassian.com/plugins/com.atlassian.jira.jira-rest-java-client/server/overview

Oh, or a ScriptRunner script looking at each custom field. Or REST API.

I think I found this using the database customfield table once

You probably don't have the home.dir/data directory accessible in the new setup

Colton, Disagreement is fine, but one of the marks of the Atlassian community is that name-calling is not acceptable. If you have a problem with Nic, contact him directly. He's not hard to find.