Nic Brough -Adaptavist- Expert

I've seen transitions with almost 100. They're very slow, but still work. On top of the standard five, I would try to avoid adding more than 10-12 simple ones, or 2-3 complex (or dependent on other systems) ones if you want the transition to execute before your people get frustrated and impatient. From a management point,…

There are almost 100 gadgets available on the first Jira I looked at. No-one is going to write an essay on that for you. First hit on a search engine for me was https://confluence.atlassian.com/display/GADGETS/All+Atlassian+Gadgets and if you read the links for each gadget on the link you gave, they are documented there…

Start at https://confluence.atlassian.com/adminjiraserver/project-screens-schemes-and-fields-938847220.html

That is an essay question that would be best answered by copying and pasting all the documentation. That's not what we're here for. I recommend you read the docs for the gadgets.

* Autowatch tells Jira that you want to add yourself as a watcher to issues you comment on. * My changes tell Jira to email you (or not) when you make a change and you get included in the list of people to be emailed about it (Most of us turn this off - I know I just changed the issue, I don't need an email to tell me what…

Status is not really a field, it's an indicator of where an issue is in the workflow. The "create" process can only land on the first step of the workflow, so, no, there's no way to start a process in the middle.

No, there are no built-in functions that allow for partial visibility of a page. You might finds something in the marketplace, or possibly write a user macro that can do what the "hide" macro does based on the groups of the logged-in people.

Try def customFieldName = "Name of your custom field" def chkBxFld = customFieldManager.getCustomFieldObjects(issue).findByName(customFieldName) assert customField : "Could not find custom field with name $customFieldName"

Those two phrases lose information that the current one gives us, and both could, and would, be wrong. It tells us that Jira had failed to start, but has now been restarted. * "Jira has failed to start up" is incorrect, as Jira is now running ok. * "Jira failed to start up" is better, but is potentially misleading, as…

Plugin settings are for storing settings related to the configuration of the app. If you had things like the plugin is looking at a particular field or had options like limiting it to certain groups. Active objects is where you would store data that you want to keep. It has constructs that support things such as tables in…

There is a "time in column" indicator on cards (a series of dots), and if you hover over it, a tooltip will give you the actual time in column.

There's nothing to "check". But you should be aware that converting from Service Desk to Software means the project will lose all the service desk functions (portal, requests, SLAs, etc)

Yes, it is true, it's a copy of a bit of the documentation. You will need to ask your administrators to give you the access you are asking for.

Yes, you'll find those icons are click-able. The permissions are not that fine-grained, if the icons appear, you have edit rights. However, you don't need to. There is no post-function setting the resolution. I suspect the screen for the transition has the resolution on it. That will set the resolution as well.

The options selected are not strings, they are option objects. If you want to work with just the option's name (as it appears to your humans), you should use .getValue() to get the name out of the option.

You have to have admin rights, then you can edit the workflow and see the post-functions on the transitions - clicking on a transition in the diagram editor pops up a box with a selector for conditions, validators, post-functions etc (and you add/change/delete them from there)

Is FieldA really a text field? Also, I would simplify - the "user" object should be a jira user object, not a string, then you can just use issue.setAssignee(user) without having to cast it from the assigneeX and then look it up.

Click on the "page information" option in the tools menu. There is a shortened url link in the top left information box.

Ok, you'll need Prometheus to make calls to the rest API - start at https://developer.atlassian.com/cloud/jira/platform/rest/

It is what it says it is. You have a field, you have hidden it, you have made it mandatory, but not set a default. You will need to un-hide it, make it optional or set a default for it. I think you have misunderstood what a mandatory field is. When you make a field mandatory, you do it for the entire lifecycle of the issue…

You will need an automation or scripting app to provide a listener function that can spot the log-work event and clear out your custom "date started" field (it's not a system field, Jira doesn't have a date started field built in)

If you add any ScriptRunner "behaviour" to the field, then it will disable the inline edit function (which, I find incredibly annoying and never do). There's a sentence in https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html that describes that function

The behaviour is logically correct and dumbing it down reduces the flexibility of search.

The "as String" inside the switch statement is either pointless or going to fail to do what you want. If FieldA is a text field holding a string, you don't need to convert it to a string. If FieldA is not a text field, then you're going to get a representation of the object it contains, not a simple string with the name of…

I don't understand the question. I suspect when I say "short link", you say "tiny link", so they're the same thing.

What do the docs for the connector say?

None - the numeric strings you see in the string values are the ids of the options in customfieldoption

I have not found any way to use OAM/OID as a user directory for the Atlassian suite.

I am sorry, but your description does not explain what you are doing. Why are your people having to register? Is it because you are asking them to use a Jira Cloud system that requires accounts to access it? And your video is an attachment to an issue? If so, then yes, it should work this way - your people need an account…

There are other apps that provide validators, but because ScriptRunner lets you write code that hooks directly into the Jira API, none are quite as powerful as it is. import com.opensymphony.workflow.InvalidInputException def cf =…