Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! There is no way to remove the summary of an issue. However you are working, the summary is what your humans use to tell you what is not right or needs improvement. Your processes should incorporate "what the summary says" into everything you are doing, even when you set up a help system…

Welcome to the Atlassian Community! The "changed link" data is not dependent on the project. (If you look in the database, you'll find a simple table with two columns - one contains the text of an issue key, like AB2-123 and the other is the issue id in the database - the number that doesn't change when you move an issue)…

Sorry, couldn't remember the last client who had this problem, but I found it: mysql> select @@character_set_database, @@collation_database, @@character_set_server ; +--------------------------+----------------------+------------------------+ | @@character_set_database | @@collation_database | @@character_set_server |…

No, that's not what is happening. There are two parts to this report - the search and the actual report function. The report function takes a list of issues and displays them in a particular way. In this case, you've chosen a pie chart, segmented by reporter. Your "saved filter" is the problem, it is selecting for all…

Welcome to the Atlassian Community! You will need to read the logs to see what the problem is. Start with <jira home>/logs/atlassian-jira.log but check the other files in that directory too.

There are three settings to look at, and you need to be very very careful about the exact names you are using. Give me a few minutes, I need to go look up what the third one is.

Welcome to the Atlassian Community! A "refuse to connect" usually means the site does not exist, but it can also mean that the site exists, but you have no permission to use it. I suspect the second case - your connection from Tableau is not configured to use an account that has access.

You don't. There's never been an option to do that.

It's not possible. An issue must be of a type that exists within the project. There are a couple of tricks you can play to prevent creation of the "wrong" issue type, but you can't delete them from the project. (Scriptrunner's Behaviours can remove the option from the list, or you can put validators on the "create"…

Yes, you can move defects between projects. You should always avoid doing this though, it's complex and structural.

Sub-tasks are not sprint items, they don't go into a sprint. I mean, they do, but only because they are a part of their parent, they are not independent of their parent. So you can't really say they are completed in any sprint, it's not relevant data. You should be reporting on their parent You'll have to come up with some…

It's not unusual to see the project only using one workflow, but it's perfectly possible to use different ones by issue type. The "workflow scheme" for a project is the way Jira maps the workflow to the issue type - build your new workflow(s) (I recommend cheating -- copy and modify someone else's work, it's faster than…

Microscope only gets you some of the information. We've got a pile of improvement requests for more of it to work through, but for the things that are not not in it, you should log in as an admin and simply read the lists. Physically looking at each one is a more simple and quicker way to get the info you want than reading…

I don't think it can execute the if statement. You start it with "if (afVal ==", but your script does not define afVal, so the script has to evaluate the if as false. I think you need to add a line like def afVal = af.value or change line 1 to def afVal = getFieldByName("Affected Artifacts").value

You could do this by removing their "edit" permission in the space, or by restricting the pages, setting them so that "edit" can only be done by certain groups.

Jira formats date/time fields in two ways * as an absolute date or date and time as you see in Created and Updated in your screenshot, * as a relative date/time which is fuzzied up to save the humans having to work it out every time. You've not got one of them in your screenshot, but it'll show things like "a few minutes…

Ok, that's what it says it is, you've tried to connect to a page that needs you to be logged in to see. Your integration needs to log in with an account that can see the page before it can get a copy of it.

I do think it should be in the history of the issue the sub-task was moved from, even if it's just a line saying "used to contain these subtasks: <etc>" so that you know and can go look at the history of the sub-task if you want to know exactly when it moved.

To do this, you would add the three fields to the same screen your drop-down field is on, and use a behaviour to show/hide them depending on the selection. https://library.adaptavist.com/entity/control-form-field-based-on-selected-checkbox-value shows you how to do this with a checklist field rather than a drop-down, but…

* What do you mean by "login"? * Jira does not record when a project is created, apart from a line in the audit log. Project creation is not necessarily the project start date either, that's probably something you want to record elsewhere (or have a rule to derive it, like "project start date = creation date of the first…

Yes, a user can edit the settings for gadgets on a dashboard if they have edit rights for the dashboard. The person who created the dashboard is automatically an editor, but they can edit the dashboard and name other people as editors.

* Go to Admin -> manage apps and install it. It's a one-off action, that should always be a conscious decision by a human admin, there's no point in looking for XML or other automations. * You can write one - if an action fails, the response will tell you so and you can code to re-try it. * Changes are atomic and…

Welcome to the Atlassian Community! I'm afraid there's nothing we can help you with here. You need to take an exact copy of the content of the "licence key" field for your Confluence server from https://my.atlassian.com/products/index (the text in there has no line breaks or special characters, but actually the server…

Welcome to the Atlassian Community! This looks like your project is using a different priority scheme to the one you have shown in the screenshot. Could you check which scheme your project is set to use?

Boards are not containers for issues (projects are), they are a view of a selection of issues. If you make a new board for your customers, you can draw in whatever issues you want from any project (and it doesn't matter if those issues appear on other boards) But you're going to have to revise your permissions - you say…

You don't set up the create screen in the transition. When you create an issue, Jira uses the create screen that has been set up in the "issue type screen scheme" for the issue type you are creating. In some places, it won't pop the create screen at all - there are a couple of places you can do a quick create. You can…

Look at the "workflow scheme" for the projects - this tells you what workflow is used by which issue type in the project. You'll be able to map the same workflow project 1 is using on to the issue type behind "new feature" in project 2. Note that this is the workflow for the issues, not the requests. Requests do not really…

Very simply put. minimise the number of people who can make changes and make sure they are in a team together. My standard recommendation is that you should have a Jira project to track all change requests and a team of ideally 2.5, but maybe up to 10 for a very large DC suite. (The 2.5 is two people with admin rights and…

Yes, they are dynamic - whenever you visit or refresh the dashboard, or a gadget gets refreshed because you set it up with a regular refresh interval, the filter is executed and the chart rebuilt. The chart dynamically shows the results for the filter results as of "now".

Without an example of where you think they're wrong, we can't do any debugging with you. All we can tell you is that it's likely to be down to one of * Your email client not rendering them in a way you'd like * You've customised the emails and broken the formatting * You just don't like what Jira is sending (which is fair…