Nic Brough -Adaptavist- Expert

I am sorry, I still do not understand. Are you saying that you are using different fields in different projects and then expecting the export to know how to merge them all?

Remember that you will need to get DC licences for Apps too - they will stop working if you swap to a DC licence for Bitbucket (In most cases, it will just be a DC licence for the app, but there are a couple where the install is different for Server and DC, and you may need to install a DC-specific version of the app)

The "created" field holds and displays the date and time of the creation of the issue, "updated" shows you the last update. The history records all change to an issue, including all status change, and those records show date and time as well.

Start at https://support.atlassian.com/jira-cloud-administration/docs/work-with-issue-workflows/

You can't do this. The last column is "done", and that's it. You need to include all your done status in the last column for it to work. There is a common question of "why don't we allow the done column to be further left, having 2, 3, 4 etc columns on the right being done". This would sort of work, but it is missing the…

Welcome to the Atlassian Community! A board is a view of a set of issues, not a container for issues. You can use a Kanban board to view and report on archived and completed items if you want, but your issues won't be stored in the board. Projects are the containers for issues.

Welcome to the Atlassian Community! The default workflows are deliberately kept as simple and minimal as possible, not everyone has CABs. If you want CAB approval in the workflow, you will need to get one of your admins to add it.

Welcome to the Atlassian Community! We can't do that. None of those fields are standard system fields in Jira, so we can't tell you how to access them, as they could have any ID. They also look like they may be coming from a test management app. If that's the case, you probably want to be using the REST API for that app,…

Welcome to the Atlassian Community! To add a due date, click on the due date field in edit mode, or fill it in when creating the issue. If the field does not appear, talk to your administrators - it's either not configured for the project and issue type, or you do not have "schedule issues" permission in the project.

Welcome to the Atlassian Community! In your automation actions, look for "transition an issue". Status is not really a field, it is a display of where an issue is in the workflow. Issues undergo transitions to move through their workflows, and a transition will (almost always) change the status.

It's not the batching that is the problem, it's what your VPN is doing with the results. The batching is fine with most other systems, and it's done to standards. If your VPN doesn't support standards, you can't expect someone to have to code for non-standard things. Edit - sorry, that was a short and terse response, I did…

The transition between the two status needs to have a "transition screen" set. The screen doesn't need to have any fields on it, if the user has comment permission, the comment box will appear there and let them enter a new comment.

Heh, the Connect framework has been quite superseded by Forge. Start with a read through https://developer.atlassian.com/platform/forge/

You'll need to encode them if you want to do that. Spreadsheets don't encode when they export.

CSV and Excel files are different. CSV has no support for formatting, it's plain data. If you save a spreadsheet file as CSV, your spreadsheet can only save the data in a standard CSV shape, without formatting or cleverness. TLDR: you can't do this, because CSV does not have formatting.

Ah, the screenshot showed us that, and more! Thanks! That screenshot suggests that you've started a sprint and then started adding stories into it.

Could you describe "can not create" please? Is the user offered the issue type drop-down when they click "create"? Does the create window not appear? Is there a penguin growling at them when they reach for the create button? Can they enter stuff, but get an error after entering the issue details and clicking create?

Welcome to the Atlassian Community! There's no need for a quick-filter for that. On a board, your completed issues are, by definition, in the right-hand column on the board. If they're in any other column, they're not complete. So you just look at the last column, there's no need for a filter. You might benefit from a…

The only ways to do this without any apps are * Disallow the users "create" in all projects that have Epics in them * On the create transition for Epics, put in an impossible validator for the users (Ugly because they will lose a lot of their entered data when it rejects their request to create)

Welcome to the Atlassian Community! The only way to do that would be to write an app that can provide your templates and automated actions.

Does your sudden line co-incide with when you move your active issues into the last column on the board?

Yes, if your Jira platform (core) is licenced for DC, then everything you add to it will need to have a DC licence applied to it. (Applications and apps can arrive in a few formats, OBR and JAR being the most common. Note that in a lot of cases, the software is actually identical, when you're getting an app for DC, it's…

Welcome to the Atlassian Community! My guess is that they have access to create issues in a different project, which has a different set of issue types available in it.

Welcome to the Atlassian Community! Can you confirm that your Dev and QA activities are done by two separate teams, who have their own backlogs and sprints?

You have to make the field optional. The email handler can't know what to fill in to a mandatory field.

That's because you don't do the change from here, you have to change the issue type in the issue type lists. In fact, you can't convert them. You'll have to rename "Task" to something else (temporarily), then create a new Issue type called "Task", selecting the sub-task level for it instead of issue level.

Yep, it's the formatting. Look at the content that contains the Blah Blah Blah, you will find the line itself and another one that are formatted as "header 2". (I think it'll be header 2, can't be sure) The heading formatting applies to an entire line, not just highlighted text

You have to report on the various different actions differently, and there's no record of just "updated". You can look for individuals "was updated by (Bob Smith)" for example. But yes, all record of change is stamped with the author and that is indeed all logged in the issue history.

Jira Software projects and Jira Work Management projects are intended to do different things in different ways (still issue tracking at their heart, but different processes for it), and hence look different.

When you're using subscriptions, you are actually running a filter to find a list of issues to tell people about. In a filter, you can do things like "and reporter = currentUser()", which would limit the report to the person getting the subscription.