Nic Brough -Adaptavist- Expert

You take off whatever it is that marks a project as archived. In DC and Cloud Premium systems, it's a simple flag. In server and standard Cloud systems, there's no archive function, and people do varying things to "archive" - usually change the permission scheme to one that disallows any change in the project.

You have to be named as a site owner in order to raise support request.

It's a workflow that contains all possible status, so we don't lose the current status of an issue when we flip a project over to using that workflow (done so we can delete the original workflow that we won't be using any more) It won't appear in the inactive list, because it is in use by (archived) projects.

You can not "disable" a scheme. The active/inactive flag is simply an indicator of whether an object is in use (one or more projects are associated with it). The only "archive" you can do with schemes is "not delete it"

I don't think that error message is the right one in a lot of cases. I suspect you are using an Atlassian account which is not named as a technical or billing contact for that Cloud site.

SR lets you use the whole of the internal java API directly, which, of course, has to be able to read custom fields. Depending on where your script is running, you may use different methods, but in most cases you will be using something like issue.getCustomFieldValue( <custom field object> ) You may find it useful to spend…

Correct, you are safe. A filter is just a definition of a question - "show me issues that match this criteria". Deleting it has no effect on the issues that it might be returning. Issue deletion only happens if you delete issues explicitly, or delete a project.

You will need to raise a support request (which I suspect is a cosmetic bug) with Atlassian over at https://support.atlassian.com/contact

This makes a lot of sense to me. I won't bore you with my journey (unless you really want to know about Errol the CI dragon), but I can say that CI/CD was what routed me into Agile. It's a natural fit, I think grouping them together here makes a lot of sense.

That is the best one so far, for me. "Erudite" is a word that I would try to use if I was ever asked to write a reference for you, it's a superb fit. I never realised it was part of a name anagram too! 

Ok, so to answer the points first #1 - those are not friendly names, like "Overview" is #2 - yes, with emoji-that-doesn't-help-Overview as a name It's not "tech debt", it's "we designed it this way". Most wikis don't have duplicate page names, in fact Confluence is weaker on this than most because it allows you to use the…

I'm going to blame you if anyone calls me Oscar at the next Summit!

Welcome to the community! I'm afraid I only have clarification questions: 1. Are you creating new issues, or trying to update existing ones? 2. Do you have at least one sub-task issue type in the project you are trying to import into?

Ah, bother, that's the one that always bites me too. Almost every time, I've missed the permissions on a project! Well spotted!

Ok, makes sense, you want some form of "assignee vs account" report. The immediate thought is my go-to to get people started on this sort of reporting - define a filter for "issues updated during yesterday" and then view it via a dashboard with a "two dimensional filter" on it, with the axes set to assignee and account.…

Moving issues between projects is not a minor task, there's all sorts of checks you have to do to make sure data integrity is retained and, quite often, ask the humans for more information. You can, of course, get your people to do this by hand, but automating it is beyond the ability of most things, it requires quite a…

Ah, asked of someone who spends too much time on crosswords... The name I use all the time has a few, but only one really stands out - I sometimes get called Oscar because, well, "Bin Grouch" My full name gives us stuff like: * Isochronal bug * Hog binoculars * Bonus oligarch * Bah, Colourings

That's correct, the assignee field is single user, trying to copy a multi-select into it is nonsense, the data structure isn't supported. You'll need to use single-user fields, or do a bit of coding to decide upon and extract the account you want to assign the issue to from the multi-select data.

Edit the page and remove the macro. (I think there might be more to this question, but you'll need to explain more if there is)

How are you defining "productivity"? (Or recording the underlying numbers you use to work out a metric?)

It's not quite what projects the boards are selecting for, it is more what they might be selecting for. What are the queries for C, D and E? Could they be drawing in projects you're not really expecting them to (even if they'll never find an issue because of your data structures, could they be looking at another project?)

I want to divide this into three parts, as the answers are different: See projects: Yes, enable anonymous "browse project" access to the project(s) you want the world to be able to see. Create issues: In theory, yes, enable "create issue" as well as browse. But. You won't know who is raising the issues or have any easy way…

I've seen this done with a scripted field on server, that was able to rummage through the history to see where "close sprint" had pinged a story over to another one, and count the number of times it had happened. JQL for "sprint jump count > 0" was then a simple clause. But yes, it's a pain without coding, I don't think…

Oh, sprints, yeah, they're not options, they're sprint objects. I've never looked for them, but I do believe most of the sprint data is in the active objects tables that Jira Software creates. Tables are prefixed with AO_60DB71 (crib sheet for which app creates which tables is…

Ah, that would explain it, one of the accounts is a site admin, but you have logged in with the other (who is not a site admin), so now all the Atlassian stuff thinks you are the unprivileged one. I'm afraid there's no easy way to work with two accounts at the same time yet (it's a very popular request). I usually do it by…

Time estimates are not story points, they're time. Whilst it is absolutely fine to use both of them at the same time (estimate and burn down in Story Points, log time worked in the time-tracking is a pattern recommended by Atlassian), they are not the same thing. You can set your sprint estimation statistic to any numeric…

No, there is no functionality in Jira for creating new layers of heirarchies. You should indeed be looking at Advanced Roadmaps (Portfolio) for this, but there are alternatives such as BigPicture, EasyAgile and so-on. If you really explicitly want to do this as an issue type, take a look at Structure though, that does let…

Go to id.atlassian.com , log in, and edit the profile. You can change your name there, amongst other settings. It may not have an immediate effect in all Cloud systems, you may need to wait a few minutes. From google translate: จากกูเกิลแปล: ไปที่ id.atlassian.com เข้าสู่ระบบ และแก้ไขโปรไฟล์…

Jira reads the server.xml when it starts. So a simple stop and restart should pick up your changes. From google translate: 从谷歌翻译： Jira 在启动时读取 server.xml。 因此，简单的停止和重新启动应该会接收您的更改。

>jira global admin but for specific project(s). Cannot be done. Most of us "work around" it with apps that enable something like it, or more often, automations that allow project lead type people to request new projects as a support call (I did it with Jira issues, handy as you got an automatic project register fall out,…