Comments
-
Bother, I was hoping for a clue in there, but that filter is fine. Do you have any quick-filters set up (and applied) to the board?
-
I don't think you are, if you log in and it tells you that you have no permission to use it.
-
Yep, perfect. The second screenshot ruled out the problem I was thinking it might be. Could you show us the board filter too? The full text of it (again, feel free to xxx out anything that's content, like "and assignee = 'charlie' " could be shown as "and assignee = 'xyz'")
-
This suggests that during the migration of the schemes, you are telling Jira to change an issue type from a story-level type to Epic. And you have one or more issues at that level that have their epic link field filled. Either map them on to another issue type at the story level, or remove their epic links before migrating.
-
You'll need to talk to your administrators - it looks like your permission to use Jira has been removed.
-
Ok, so not "no transitions", just starting simple with a full set of "all" transitions. You should add transitions (replacing all) when you have a process that is constrained. For example, the original Jira workflow was a map of a process that Mike and Scott wanted to follow. Broadly, it is Open -> in-progress -> Resolved…
-
Ah, ok, I had not picked up the main problem. It's not security, it's performance. I don't think you can do that on Cloud unless you are using Atlassian Access for the users.
-
Yes, team-managed sub-tasks don't yet appear on company managed boards.
-
The hierarchy is under Admin -> Products -> Advanced Roadmaps hierarchy configuration But the place you need to look for this is actually in the project. Go to the project you are trying to create the issues in, and look at the "Issue type scheme". What types of issue do you have listed in there? Look at their "level", I…
-
Welcome to the Atlassian Community! Could you show us the full issue view of API-1079 or SUP-315 (we need to see the summary line down to where the activity/history tabs start. Please do obscure text if you want to, we're not interested in the content of the fields, just the structure.
-
It happens when your account has no permission to use that workspace. You'll need to talk to the owners of it.
-
Welcome to the Atlassian Community! No, the free version does not limit user maintenance. What exactly are the symptoms of "I can't create and manage the customer"?
-
There are two things this is almost always down to: * There are conditions in the workflow that are blocking you from using the transitions * You've got broken status data in the database, caused by a crash or a broken app or script You'll need to be an admin to diagnose what this is: In the first case, please go look at…
-
On Server and DC, Jet is implemented as a "plugin" - it runs within Jira, uses the database under your installation for storing its data, and makes no calls out to external systems. Jet is an Atlassian "product", in the sense that it's a couple of apps that they write and maintain (a couple because the server/dc and cloud…
-
Your approach doesn't work if you're doing anything like Scrum or Kanban. A sub-task is part of its parent story, and as such, shouldn't be assigned to anyone outside the team that the parent story belongs to. In your situation, the better practice is to create two stories, one for each team, and link them together to…
-
Actually, you'll have the opposite problem. Because people can't create pages where they think they should be, they'll go create them in an even worse place. There used to be an app that could stop people creating pages in the wrong place. The handful of people who installed it found it made their mess even worse,…
-
There's no reason to block people adding pages to a space. It just doesn't make sense to say "no, you can't create a page" arbitrarily.
-
No, the length-of-time display is a global setting. It has to be, otherwise you'd be getting nonsense from cross-project reporting.
-
Ok, I don't know Sharepoint's remote API at all, so I have no idea how to code for it, but you will need to code a post-function or listener that can read an issue's attachments, decide if it needs to go over to sharepoint, work out where, and then duplicate it into Sharepoint over the remote API
-
To get the ID of an attachment, you have to read the issue for its list of attached files. /rest/api/2/issue/(issue key)?fields=attachment should do it. Attachment ids are all unique, irrespective of the file content and name, you'll need to read every issue that has been affected.
-
You have re-indexing options in Server and DC Jira and Confluence, but Cloud handles it all for you and you can't trigger a manual reindex.
-
Welcome to the Atlassian Community! JQL is for finding issues, it has nothing to say about the data on those issues, that's up to how you are using the reporting. Your "sheets" don't matter to Jira (unless you somehow import them) To merge projects though, the most simple case is to search for a pile of issues and then use…
-
Welcome to the Atlassian Community! Yes, Jira only has one project lead. I prefer the word "owner", but it's not that important, and I'd have no problem if the field allowed 2-3 owners. Project Lead is only one of the 12 ways to give people permission in a project. Go in to the permission scheme or the project and try to…
-
That helps, it shows us what you have, but I don't see how you have "no transitions". Both diagrams show transitions.
-
That's an interesting question, it provokes a load more. If, for some strange reason, you've been reading a lot of my answers here in the community, you'll have seen me say "Jira is an issue tracker" quite a lot. Whilst that is generally right, a lot of people question it, as they prefer to say "it is a workflow engine".…
-
It could be a breaking change, but actually, I wouldn't bother with a backup. It's not going to break anything you can't easily fix (specifically, filters), and it's far easier to make another quick change to fix it than restore a backup. (Restoring a backup - hours, renaming it back to "Epic" - seconds)
-
I'm not sure what JiraPS is, but it is doing a couple of things you need to work through. First, the bit I'm slightly uncertain of - I think it's giving you an error message which is its own rendering of the actual error it got back from Jira. Although it wasn't actually Jira, it was the Tomcat or one of the network…
-
Once you're happy with all the changes (by everyone, if you're working at the same time), click "save" towards the bottom right and it'll save everything, instantly available to anyone landing on the page.
-
So the question is how did you change the issue into Status A? I assume it was not created or imported in that status, so without a history line, we can't tell you what happened. The only thing I can think of is that you have a script which is deliberately constructed to not write anything to the history.
-
Welcome to the Atlassian Community! It is possible to do it, but it is a nightmare to do it yourself for all but the most basic tracking. I strongly recommend you look at the second and third apps you can see on https://marketplace.atlassian.com/search?hosting=cloud&query=analytics