Comments
-
That should do it after you click Publish
-
This is the official Atlassian approach to field-level security. Many admins have found that plugins such as ScriptRunner with its Behaviors feature gives more flexibility and ease of customer usage for this case.
-
Don't forget to also copy the home.dir/data to get attachments and avatars
-
I have a tendency to not fit myself into boxes defined by other people. I like to define my own boxes to check. I guess that makes my ascendant "Awkward". You should hear the intake interviews in hospital :)
-
Good points, especially about keeping it short. I would also stress spelling the name of products correctly. It's Jira not JIRA for example.
-
I've had a few moments where for one reason or another I could feel the hair on the back of my neck standing up. A very strange feeling indeed!
-
Good summary. One thing I find hard to remember is which order to make changes in. For example, create a copy of a screen before you create a copy of the screen scheme. Might be worth changing the bullet points to a numbered list at "Create a new screen"? Might also be worth mentioning what Extended Project Admin lets you…
-
Beautiful photos!
-
I would expect that to work but haven't tested it since we moved to Data Center a few years ago. It's easyish to check with a couple of eval installations. Though eval DC does need a real database even for a single node I'd like to see this addressed…
-
I've also seen it used in ScriptRunner JQL to find all the issues and sub-issues in an Epic in the past. Nested filters can have performance problems, and if uses as agile board filters Jira may not be able to work out which projects you need to have Manage Sprint permissions for
-
I see the documentation at https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-fields#Advancedsearching-fieldsreference-filter I've seen subfilters used when you want to have a list of people in different filters and only make changes in one place. For example Your first filter with example…
-
Not something I'd recommend doing because it's so central to the way issues work. You could create a workflow and associate it with sub-tasks. Then only have one status in that workflow. You'd still need to have a transition to set the resolution on the sub-tasks when you didn't want them to appear as active. A better idea…
-
I’d start with empty instances and cut and paste the wiki pages youneed
-
Lego too, including this beauty from 1977.
-
Oh yes indeed, I remember writing some essay about Rome using details taken straight from Asterix the Legionary. Cool that you had them in four languages.
-
And Jacques Cousteau books. And space books. And Guinness Book of Records.
-
Books were my thing. Lots and lots and LOTS of books. Tintin and Asterix are particular favourites.
-
When asked by a child how old she was, my mother replied "as old as my tongue and a little older than my teeth". Which gave them something to think about at least.
-
https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Unlock-a-field-with-Script-Runner/qaq-p/445687 has the scripts to lock and unlock a field
-
Depends on how many versions you are skipping over. If all the versions are reasonably recent you can probably choose any order. And of course this is in staging. If the versions are very old I guess I would do Jira and then Confluence then the others, as you noted.
-
I'd start at marketplace.atlassian.com and look for Salesforce
-
Looks like the Reporter field needs to be added to Create or Edit screens in some Jira projects
-
https://scriptrunner.adaptavist.com/4.3.9/jira/fragments/HideUIElement.html is a starting place, though for an old version
-
Possibly with ScriptRunner in Server/Data Center
-
There are two options named "ScriptRunner for Jira " with the Cloud and Server bits cut off when I've tried. If one looks wrong then try the other.
-
Very clear article, thanks!
-
Off the top of my head, the things I've valued over the last 25 years of handling incidents are: 0. Plan for the disasters. Test the plans. Assume the worst will happen. 1. Have separate people to handle communications. And all communications should say when the next communication will happen 2. Change only one thing at a…
-
https://en.wikipedia.org/wiki/Statler_and_Waldorf
-
If you mean the custom field id it's the number after cf[
-
Sliding down the stairs with your head first. On your back if you dared. Stopping a bike always involved a 180 degree skid when I was ten. Using the dinner cutlery outside for anything was a very risky game.