Comments
-
Nothing. Assuming they do the right thing and just flag your account as "not active", then it just means they'll see (inactive user) next to <your name> on stuff. If they do it wrong and delete the account completely, then it'll change to <your login id> (unknown user). Nothing will stop working, unless you've coded your…
-
What does "I could not set it up" look like? Errors enabling Insight? No links or fields appearing? An annoyed penguin jumping on your keyboard every time you reach to click on a link to it?
-
My guess is that it is working fine, but you are not looking for issues that do not have any label (which is not the same as "has a label which is not X", which is what your search says) I think you want to search for both cases: and (labels != CR or labels is empty)
-
Welcome to the Atlassian Community! One of your admins is adding the field, you'll need to tell them to stop doing it, or remove their ability to do it. Check the audit log for a starter, that tells us when admins are creating or removing fields.
-
Read the issues over the REST API - when you use that to get issue information, the response includes the history of the issue, including the work logs and when the issue changed from "unresolved" to "resolved"
-
Only one I've seen is "use something that doesn't hog your bandwidth"
-
Sprints are not project artefacts, they are independent of them. They are created by boards, which are a view of a selection of issues. A sprint contains a sub-set of issues that the board selects. A sprint will be shown when issues you have chosen to look at could be in it. So you are seeing the sprints that you don't…
-
This won't work. It's not working because it has not been coded for, because you can't code for it in the way you are assuming things work. There's nothing to "fix" here because you're trying to do something that can't be done. You are assuming that "create an issue in this project" will create a series of issues that will…
-
Yes, include a "if field 'type' = " block in the automation.
-
Permissions are a project level thing on the most part, so start with a look at who can do what in the permission scheme for the project. On an issue level, you can hide individual issues with issue security schemes but that is only "can I see the issue at all" and based only on a "level" field, it can't work off other…
-
I think we need to drill into what you mean by "documents"? The instinct is to assume you mean attachments, which may or may not be described by the word "document", but I don't want to guess that this is what you really mean. (If it is just attachments, the simple answer is "does your migration method deal with…
-
You don't want to "solve" this "problem" Unresolved issues do not have a value for resolution. That's the way the data works. Jira displays unresolved when the resolution is empty, but that's a convenience for the humans, it's not the actual data. When you export, you just get the data, there's no code to help you…
-
That's a very interesting question. I work for a partner, one with products, but I personally try not to answer with "you'll need <adaptavist product>". I find the knee-jerk marketing responses from some other partners quite grating when it's "use our app" instead of "here's how you can do it natively" or even "this is why…
-
Welcome to the Atlassian Community! You'll need to work with blueprints to do that. See https://developer.atlassian.com/server/confluence/confluence-blueprints/ 欢迎来到 Atlassian 社区! 您需要使用蓝图才能做到这一点。
-
Welcome to the Atlassian Community! Posting an answer to a question on an issue is a change to the recorded issue. I am a little bit lost on why recording that someone made a change is a problem for an issue tracking system (the short answer to your question would be "yes, that's what the software is for, recording changes…
-
@Steve - I'm just pointing out that you can't do this (because it's nonsense). It's no good "helping" people to do something they can't do, you should be trying to help them understand why it does not make sense. I'm sorry I've not been clear enough when trying to help, but I'm not going to stop trying to help people when…
-
Welcome to the Atlassian Community! What do you mean by "split"? What are you trying to do with a workflow scheme?
-
Ok, I'm a bit confused on one point. Are the assignees on the sub-tasks set with the first automation or the second? "First automation: If [...] specific subtasks are created and assigned." "So the subtasks are assigned when the second rule is executed" My other clarification is on the second rule (I'm afraid my German is…
-
Where are you doing this "if I select project X" and "if I select project X and Y"?
-
That is not quite what the diagram says. The diagram says you started the sprint and then added a load of estimated issues into it. (I've emphasised started because started and created are not the same thing) Could you explain if that is what happened?
-
"There is no "actual" vs "estimated", it's the same number. The sprint estimate is for measuring what you commit to vs what is delivered," >A sprint is defined in days. No, they aren't. A sprint is a timebox with a start and end. Most people talk about them in days, but the actual unit you use isn't important. When…
-
Welcome to the Atlassian Community! Probably "field changed"?
-
Welcome to the Atlassian Community! Run a search for the issues you want to report on, save it as a filter, and then subscribe your manager to it, they will get a regular email containing the count of matching issues and the list of the keys for the first handful of them.
-
Ok, there's two problems here. Story points are not estimates used for tracking anything outside the team's sprint. There is no "actual" vs "estimated", it's the same number. The sprint estimate is for measuring what you commit to vs what is delivered, not "actual". In fact, Story Points are also there to tell you that…
-
Yes, "useless" is a strong word, but it is accurate. Once an item is done, a team has no further interest in it. So what use is having a load of columns they don't care about on their board? None. >For our release team Done means when development work is released to production Ok, that's fine, that means that you have…
-
No, project roles are global, they appear in all (company managed) projects as soon as you create them.
-
It's a bit more complex as there are many ways to configure projects and boards are not necessarily linked to the projects directly. It's easier to talk about the board than the project types when explaining this. * Some boards are very simple - Jira Work Management projects have a single and very simple board attached to…
-
There's another conversation about these where Atlassian have asked us to send on spam from these dubious sites to https://www.atlassian.com/trust/report-abuse (forward the email with full headers, no more information needed)
-
When you upgraded, Jira replaced (or removed) files that you had edited away from the standard off-the-shelf install (it will have warned you about this at the start of the upgrade, but it is easy to miss) One of the files you'd customised is Jira-config.properties in the Jira home directory. This contained at least one…
-
Sorry, I can never remember exactly what the phrase is for lots of things in Jira. The "Search Template" is what we were looking for when I said "searcher". You've got the one I expected set for Release Date, so that is not the problem. Only thing now is to check the complexity of your plan to see if it could be…