Matt Doar_tzgiej Community Champion

I don't recommend adding more than about 3000 options to a Jira select or multiselect custom field. Certainly on-prem performance is not great with that.

Assuming this is on-prem, you have the right idea. Experimentally disable specific plugin modules in a test instance. Another option if you have ScriptRunner is to use that to hide (or add) parts of the UI. Some like Jira Credits are part of a larger module IIRC. Good luck!

Yes, please at least minimize the number of crossing lines. 

Well said!

I think the checkbox is still checked by default in new Notification Schemes? Something to watch out for if you don't want to allow this.

Another tip: if you create a complicated condition, then create a Confluence page to describe the condition. Otherwise users will complain to you as the Jira admin that the workflow is broken because they can never use the transition.

I recommend using a select list field not Labels for this. The Labels field searcher returns an issue and all its labels if any of the labels match the given string.

https://jira.atlassian.com/browse/JRASERVER-31291 is one place this is tracked

Labels created by scripts are useful for sure. Any label created by a person will eventually be spelled incorrectly. That's tough to avoid

If you are on Data Center and have something like ScriptRunner, this is possible with a script, lots of testing in non-prod and some exploratory coding. A quick google of "jira bulk move worklogs" suggests that the Tempo plugin will also do this in Cloud. 

What Nic said. All the things that people are putting in Jira right now may be lost. Take it out of production fast

Not an answer but https://jira.atlassian.com/browse/JRASERVER-77129 may be relevant to you

I was in a busy supermarket yesterday, just before the game started. The cashier was a young lad and all excited. I said to him "You're going to watch the big cricket game then?" "YEAH!" he replied, then "wait .... what?" There was a five second silence as he looked at me, and then finally he asked where cricket came from.…

Plus the combination of project and issue type is what allows you to customize Jira for things like workflow, notifications, permissions etc. Really important that!

I think the feature is still named Advanced Roadmaps in Data Center though

If you are color blind, you may find regular jigsaw puzzles a bit frustrating sometimes. I know I do. I quite like blank jigsaw puzzles because they have to be done with just the shapes of the edges. Which I happen to quite like sorting out and categorizing. Other family members don't think that is much fun though.…

Make life easier for yourself by using intermediate boolean variables such as isSubtask = (issue.issueType.name == 'Sub-task') then the logic will be easier to read. Document exactly when the expression should return true. Test the logic is correct outside the condition code to make the development cycle shorter.

Yes for the harder Sudoku, crosswords with my mother and then daily knowledge quizzes. 

Try it without the trailing semicolon on the last line?

Something such as an extension in your browser perhaps?

"literally turning me suicidal," - well, that caught my attention! Working with Jira and other tools will have lots of frustrations (and rewards) in the future. But if they feel overwhelming, please also seek help outside a technical forum. Very seriously, you are worth more than any tool.

What Nic said. Plus in Jira DC the existing data for a custom field in an issue is not deleted. But once a context is gone, you won't see the data again for that issue, not even in an XML dump (I think). This could be different in Cloud, but I would expect not. I have definitely deleted a global context before and then…

Tricky. I would leave the Updated system field alone and create a Scripted Field (assuming Data Center and the ScriptRunner app). The field can look at the History of an issue and determine a date value based on when there was last a change to the issue that you are interested in. Not sure about Cloud though

Thanks for letting us know. I saw username == null in some of the code. Not very obvious at all though

You're not the first to do. The API page about this has some indicators: this. https://docs.atlassian.com/software/jira/docs/api/7.4.1/com/atlassian/jira/functest/config/dashboard/ConfigDashboard.html I don't recall if the id has to be 10000 to make a dashboard the system dashboard. Likely the name has to be as expected…

"The eatery go hijacked by Daleks" As it does. But I think that story needs to be told with a drink sometime

Odd that. Any reason not to use the most common Python library to do all this? https://jira.readthedocs.io/

Lots of excellent advice in all those articles, thank you. I have too many mistakes with Jira to add them individually ;)

Absolutely, and making the test environment header color really vivid helps for me One other thing I do in a test environment is change all the notification schemes to be empty or one that won't send email. Email from a test environment can really confuse people quickly I think I also change the URLs used in an application…

Sweet photo!