Comments
-
Welcome to the Atlassian Community! Does your user have permission to transition issues in this project? 欢迎来到 Atlassian 社区! 您的用户是否有权转换此项目中的问题?
-
Not quite, but very close. I need to go back to scrum principles and how Jira has implemented support for it to explain this. Scrum works off a pile of sprint-able items (stories). When you go into a sprint, the aim is to complete a set of selected stories that your team committed to delivering at the start of the sprint.…
-
No, because the email belongs to a deleted or blocked account (in the case of deletion, I understand that all that remains is the email address) The account would have been sent an email, as per the message when they tried to get into id.atlassian.com My suggestion that used email addresses was to try to keep it all in one…
-
My guess is that something along these lines happened: * Aliss@yourold.org created an Atlassian account (or you gave them the account) * Your organisation claimed yourold.org * Your organisation claimed yournew.org * You got admin on yournew.org Alice is still managed by yourold.org, so you'll need to get admin in there as…
-
Team-managed projects do not (yet) support more than one type of sub-task.
-
You can only do this if the Invision app implements a way to do it.
-
The "solution" here is to use the tool as intended, it's not fixing the tool - there's nothing wrong with it. >If the actual answer is that sprint boards are incompatible with needing another workflow, They are not. > or set of statuses that follow after a sprint, then that is the answer. They work fine with that too. That…
-
I've been able to replicate this. I just wrote a short scriptrunner post-function and put it on the create issue transition. It writes a change of status on to the issue without going through a transition, which you should never do. So that begs the question - do you have anything that might be trying to change the status…
-
Script-runner is not the only thing that gives you validators, there's loads of things that do it, including Jira itself. Are you 100% sure there are no validators from any app or Jira on the create transition? Are you sure you are looking at the right field configuration? Go back to the project, and note the issue type…
-
Ok, that means the account has been deactivated at the Atlassian level - either the user requested that their Atlassian account be deleted, or they've been killed off by Atlassian for some reason (someone reported them abusing an Atlassian system perhaps) You'll need to get in touch with the people the email names. Or, you…
-
Yes, roles are more powerful and flexible (and as an aside, actually faster) than groups when used in permissions. You can use groups or users in roles as well, varying them by project - it's not unusual to see large installations with hundreds of projects using 5-6 permission schemes. Roles give them the knowledge that…
-
Welcome to the Atlassian Community! No, there's no way to do that directly. What you can do is hide the issues that are created with the "wrong" type. Let's imagine you've got some users - Alice, and Bob, and issue types Cat and Dog. Bob is scared of dogs, so they should not see Dogs. * Set up the project for them, giving…
-
Welcome to the Atlassian Community! Where? Grouping is something you do in the display layer (not search), and there are a lot of different ways to look at Jira issues. In many of them, grouping is not useful, or even relevant to what they're trying to do. Others do it automatically - the pie chart is a grouped display.…
-
I'm not sure what "buzon" is in this context, but yes, Jira Service Management accepts requests via email. See https://confluence.atlassian.com/servicemanagementserver/receiving-requests-by-email-939926303.html
-
Actually, no, it's not directly possible. Only Service Desk agents can be assigned issues in Service Management projects. You would have to make all of your developers Agents, and that is expensive...
-
From an Atlassian perspective, the obvious answer is "Use Confluence" - you can do some simple configuration, and then get stuck into creating your content, you don't have to worry about building a website then.
-
On Confluence Cloud, you don't care where your home directory is. But I'm not sure you mean "home directory" In the sense I read it, you're expecting a directory in a file system which you can navigate to and use the files in. In that sense, you personally don't have one. The Confluence system you are using does, but you…
-
Ahh, Sharepoint, the place where documents go to retire, unread. It is the same question though - why do you want to change the top bar? What's missing or in there that shouldn't be in your opinion?
-
I think it could be a damaged account, as you say. Have you asked them to log in to the Community here with that email address? That would tell us if the account exists or is damaged.
-
Ok, not a custom field, so the question is now what are the issue types of DTS-1216 and DTS-1217, and what do their field configurations say about reporter The message you are getting is telling us that reporter is hidden for the DTS-1217 issue type. (There might also be a quirk coming from the permissions here - if the…
-
Welcome to the Atlassian Community! You will need to talk to the owners or administrators of those boards. We can't really help you here, we're not the admins! To find them, it's probably best to ask the people who invited you - they may be the board owners, and even if they're not, they will be able to tell you who the…
-
No, you're not missing anything. You can configure Jira workflows to follow any process flow you want, whether that be a strictly controlled linear process, or a complete free-for-all. In Software development, especially when being Agile, the free-for-all end of the scale is more appropriate, and you probably are on the…
-
This error usually means that the two issues are configured differently. The source issue is configured to have fields that the destination issue does not support. So the copy process is trying to copy data to a place that does not exist. In this case, there are two possibilities: * The iissue type that DTS-1217 is has the…
-
Leave the issue key blank if you want to create a new issue - Jira generates its own issue keys when you create issues.
-
They will do calls, but only if you are a large customer with a licence that qualifies you for an account manager, or if they can't get to the bottom of the problem via the support request.
-
In a Scrum board, the way to clean up your done column is to end the sprint. You must not remove the issues from the board, that would break all your reporting. But Trudy's custom filter will let you hide them for a cleaner display.
-
You said you were using an add-on for this, can you tell us which one?
-
Welcome to the Atlassian Community! Atlassian trials are open, letting you try out a lot of the functions. You are entirely free to say "Yes, this is working for us, let's pay for it" and carry on using your trial system. Once you have chosen to subscribe to it, you can consider it your "production" system. It doesn't…
-
Welcome to the Atlassian Community! Yes, you could do this, and it's a lot better than what a lot of people try to do (add up sub-task estimates to stories), but it is not Scrum and Jira's Scrum boards are not built to do not-scrum. The best way to cope with support issues interrupting your development teams is to create a…
-
You will need to write an app to do that, or find one in the marketplace. It's not something you can cobble together with a bit of JQL and a script. I can't find anything that other people have written to do it, so it sounds like not a lot of people need it. Could you tell us what problem it would solve for you?