Nic Brough -Adaptavist- Expert

A listener can't stop an edit. It is running after the edit is complete. You could do something with Behaviours on the edit screen, yes.

Epic Link is not a field that takes options, the list is generated by having Epics exist in your system. There's no where to actually add options because that's not how it works. The best you could do is add a select list with all your own Epic links defined as options, and then have an automation that updates the actual…

Issue links do not natively define a hierarchy, so even if you had a graphical view, there would be no "under", just a link between the two issues. There are a load of apps for visualising and working with links though - https://marketplace.atlassian.com/search?query=hierarchy…

It's usually the advocate team you work with; albeit you get one dedicated advocate, you should have contacts for others. I've asked the Community team Atlassians for help though, they're good at finding the right people to talk to at Atlassian!

To check the status of the issue, look at it. The status is a system field which is almost always shown to you.

You will be able to modify the copy, as long as you have not associated it with any projects yet.

They are workflow functions that you add to transitions. A condition is a function that checks something is true. If it is, then Jira offers the transition to the user so they can do it. If it is false, it hides the transition and prevents them running it in other ways (REST, Automation etc). They run the check anywhere…

In the database. So forget it, you won't be deploying them to your install via the database. Clearing the cache won't work here, these are structural (clearing the cache often doesn't work anyway), and you'll need to trigger a full re-index of Confluence for some types of macro. You're not going to speed up macro code…

The resolution and status are totally independent of each other in the code, it is up to your admins to determine how they work best together for your process. The strike-through happens when the resolution is set. You set the resolution by having it on a create, edit, or transition screen (hint - never put is on create or…

You would need to ask your network people if they can do that if it is a Server install. Cloud premium has IP whitelisting.

Welcome to the Atlassian Community! Team-managed projects keep all their fields local to the project. Company-managed projects have several configuration settings around field use - see https://confluence.atlassian.com/adminjiraserver/project-screens-schemes-and-fields-938847220.html

The error you are getting is definitely coming from a Behaviour, so there must be one somewhere, associated with the issue type or project. Try the built-in script "script registry" to get a list of all the behaviours (and other scripts) configured in your system. That might help you identify it.

That's not how issue links work. 1) A link, by definition, has two issues, one at each end. They are directional, see https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-linking/ 2) No, the only thing you could do here is have a condition or validator that stops people executing transitions if…

You can set the workflow properties on the Inprogress status to block all those actions (except "custom fields" - the edit permission covers all fields, not just custom fields) See https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

What does "I can't" mean? Could you describe why you can't do it? What are the symptoms or error messages?

Welcome to the Atlassian Community! JQL simply finds issues that match a criteria, it has nothing to say about how you report on the list of issues it finds for you. I'm not aware of any gadgets that limit their results list as you describe.

When it's ready to be fixed, and makes it to the top of the list. Although this is for Cloud, it's much the same policy for server; see https://confluence.atlassian.com/support/atlassian-cloud-bug-fix-policy-206865884.html

Welcome to the Atlassian Community! The one warning you have pulled out of the log suggests that your Jira installation may be damaged, with it unable to find the driver it needs, but I would want to read the rest of the startup log for the full error, it may not be that.

Welcome to the Atlassian Community! Jira has a handful of self-explanatory status out-of-the-box. We don't need an explanation of To-do, in-progress, done, closed, new, re-opened and so on. Backlog and funnel are things your organisation have added, you will need to talk to your people and teams about what they might mean.

Welcome to the Atlassian Community! Please don't say "resolution status" - it's completely unclear as to whether you mean resolution or status (two totally separate independent "fields") You should be able to map a column for either Status or Resolution if you are using the admin CSV import, rather than the project's.

You can't do this - the Confluence editor does not have the functionality you need to show/hide sections during edit and macros do not execute in edit mode.

Not yet, exact search is on its way.

You might be casting objects around the wrong way. But you don't actually need to make it as complex as you have CrowdService crowdService = ComponentAccessor.crowdServicedef user = crowdService.getUserWithAttributes(userName)UserUtil userUtil = ComponentAccessor.getUserUtil()def groups = userUtil.getGroupNamesForUser(…

Yes, a line remains in the "project" table - the key, counter, description, category and a couple of other settings for the project. But all the issue data is destroyed. There may also be records in the moved issues table indicating when an issue was moved from the deleted project to another, but these are just "old key"…

Welcome to the Atlassian Community! On the command line, using git is the most simple option. For the REST API, see https://developer.atlassian.com/cloud/bitbucket/rest/intro/

It is not. That message is exactly what happens when the field configuration tells Jira the field is mandatory. I suspect you are looking at the wrong field configuration. To see the validators that might be doing it, you will need your administrators to edit the workflow for that issue type.

A is a word, one used often in text, and hence pretty useless as a search term. Most fuzzy searches have the sense to ignore it.

Welcome! There are a few criteria the Community asks for before letting people write articles, and they're not a simple set of rules. It is currently a manual flag - a mod has to set it on your account. The good news is that you're pretty close to matching - clearly identified as a partner, and nearly there on the points…

Welcome to the Atlassian Community! >I do not need the summary field in the create issue view That's not true. You need the (system) summary field on the create issue view because you need the humans to give the issue a summary.

Welcome to the Atlassian Community! Forget about this "project linking" or "sub-projects", it's a dead-end. For company-wide programmes, you should be looking at one of the scaling up apps. Atlassian has Advanced Roadmaps for that, and Jira Align if you have a bigger set of programmes to manage (starting at 500…