Nic Brough -Adaptavist- Expert

Hi, "Clone" really does mean clone, it takes a copy of the issue and all its current attributes. There are no functions for arbitrarily dropping fields or data.

As someone who lives in a failed democracy, there could be a lot to talk about, but it's not relevant to this question. The point of resolving an issue is that it needs no more attention. It's done, ended, irrelevant. Voting for something that, as @Pramodh M says, "it is done in some way" is pointless, and Jira doesn't do…

Welcome to the Atlassian Community! The short answer - put the "passed QA" status in the last column of the team's board. Note that I said "team" - your deployment people may have a different definition of done, and so should probably be using a different board to manage that. Given a workflow that should take issues…

Welcome to the Atlassian Community! The best way to do this is treat a new board as the team. Each team should have a (main) board that they all work from. That will give you a velocity chart by team! It's fine if people are in more than one team, or you create other boards for sub-sets of the teams, or to do cross-project…

Welcome to the Atlassian Community! Is this your Atlassian account that you are using to post here, or is this a new account you have set up to ask for help here?

Hi Anette, The active/inactive thing is irrelevance, it's not a setting, it is just a way to tell us humans that the workflow is not in use. Are you sure of the new name? It's not still prefixed with "copy of"?

Welcome to the Atlassian Community! Sub-tasks do not have to be locked to the same status their parent is in (in fact, they'd be useless to most of us if they were) Sub-tasks have their own workflow (which may or may not be the same as the parent issue of which they are a fragment), so they can be in different status, and…

Welcome to the Atlassian Community! I am sorry, I do not understand the question. Do you mean you are trying to restrict the field context of the Description field, like you can with custom fields? If so, then the answer is that you can not. Description is a system field, it does not have context, it's always on the…

Welcome to the Atlassian Community! There is no custom field type of "reporter", and the reporter field listing is based on the permission for the ability to create issues. You could add a user-picker, and limit it to a list of people in a role or group, but it wouldn't be quite the same as "reporter"

She was always a Cloud first cat... that's why she's in charge of all the Cloudies in the house!

Morticia hasn't changed much in the last couple of years (she's 5 now)

Welcome to the Atlassian Community! If you are an admin and on Cloud, go to Admin -> Projects and look to the left for "trash". Projects are put in there when you click and confirm delete, and you can recover them from there. They will expire, and vanish, but you have 60 days I believe. If they are not in there, then the…

Hi Sina, That error message is mostly given when a Jira system can not reach itself over your network. If you were to log into your Jira server and run something like "wget <base-url of your Jira>" it will return an error. This is a useful test actually, because it will give you the underlying error. The three usual…

The account you are using for the REST call needs to be granted "create issue" permission in the project.

I'm afraid that answer is wrong - if a field is mandatory by the field configuration, you it is mandatory on create and edit. You can not blank it out.

Behaviours works on the front end - the page in your browser. Field configurations work on the back end, as I said.

If you set a field as mandatory in the field configuration, then Behaviours can not stop the mandatory flag from kicking in and demanding that you fill the field in. That mandatory check is not done on the screen, it's done after you try to commit the issue. You don't say what app you are using to provide the issue-picker,…

Welcome to the Atlassian Community! I think you might be in the wrong place, your question does not seem to be about an Atlassian system. I suspect you have clicked on "help with the system in use for documentation or issue tracking" instead of "help with the product".

Hi Per, Simple answer - you can not. If a page cannot be seen by someone, then you can't bypass that security with an include or excerpt-include. You need to make your inclusion library public (at least to your end-users)

In a company managed project, the permission scheme is the controller - you'll find make comment, edit comment and delete comment permissions in it!

Welcome to the Atlassian Community! Workflows do not apply to boards, they apply to issues. If you give your two sets of issues different workflows, then a board that selects them can be configured to show them on the board by mapping the status into the columns.

Welcome to the Atlassian Community! You will need to talk about your network administrators about the block they've placed on that site.

Welcome to the Atlassian Community! Please take note that the Community is not support, we have no visibility of your raised requests, and can't deal with them. There are some Atlassian support people active here, but they will be working off your request, the most you'll get here is a note saying that they've talked to…

You've used a key for "user" and then named a group as the target. That won't work because groups are not users.

In a company-managed project, you could also grant your developers "comment" - then they would be able to leave comments on the the issue, ones that would not be visible to customers. Most of us allow that - the Agent is in charge of the conversation with the customer, but the developers who get drawn into issues usually…

You have not explained how these tables are being done in Jira?

Hi Michelle, The easiest way to do this is by using workflow properties to override the project permissions. You would remove the "can assign issues" and "comment" permissions with a couple of properties. I'd recommend thinking about blocking "edit" as well! Force them to reopen if they want to update anything!…

Welcome to the Atlassian Community! * Not really, they're just a unique identifier for the issue. They can be used to construct URLs for external systems to link to, as well as being the unique identifier, but that's about it. * No. If you delete an issue, you have damaged that issue. Or rather destroyed it. Deleted issues…

Ok, that depends on whether the project is company or team managed. In a company-managed project, you need to go into the "permission scheme" for the project to check the project browse access, and possibly add a new role to it (only Jira admins can do this, not project admins). I tend to have a global project role called…

Hi Coline, That would need you to be adding a link when you are creating the clone, and giving your developers the permission to read the JSM project (you don't need to give them any more permission than just "browse project") You might find it easier to use "create linked issue" rather than clone and move - that will…