Comments
-
No-one should have access to your database, it's the worst way to look at Confluence data you can possibly imagine. Only your system admins should have that, and even then, it's only for identifying and fixing some very specific problems. @Mike Rathwell has already pointed you at the right answer - an admin can use the…
-
SQL is the worst possible way to look at this. For housekeeping, go to the list of field configuration schemes and delete all the unused ones, then go to the list of field configurations and do the same.
-
My guess is that your board fitter excludes the test status or the status is not mapped into a column on the board
-
This is why you should not be looking at the database. The problem is not the table being empty, the problem is that you are looking at the wrong thing.
-
The short answer is "yes" But "take some data and push it into another system" is not a short answer. Jira accepts data from anywhere, as long as it can understand it (and it has been accepted by security), but you need to look at what you want to send and how....
-
Yes, it bases the burndown on "done", but your "ready for testing" column is not "done". From the screenshot, there's nothing complete yet.
-
Yes, that's not a Scrum approach, it's a lot more Kanban. You should use the process that works best for you, and get your tools to support it. With Kanban, you don't need to "unlock" the sprint field, Kanban doesn't have sprints, so there's nothing to unlock.
-
Excellent! Well, for that part of the problem anyway. The next question is what have you marked as "done"? The red line looks at "done", which, for Jira, means "issues in the sprint that you have moved into the last column in the board".
-
Yes, your code is just setting up a workflow scheme, it's not looking at any of the migrations or changes you need to do when you do that, including all the indexing and caching. What is your app actually trying to achieve? What problem is it solving?
-
That is very true. But it doesn't change the fact that Scrum tools tend not to work for non-Scrum processes, or that defaulting a sprint is a complete failure to be Agile.
-
Welcome to the Atlassian Community! Hard to say when you have not explained what the rcarz/jira-client might be. If you could expand on that, we might be able to help
-
Welcome to the Atlassian Community! You can't just jam a workflow into a workflow scheme, it's a structural item, and you have to check and then migrate everything currently using it as well. Your code is fine for *inactive* workflow schemes (ones not used by any projects), but it's not doing any of the work you'll need to…
-
Interesting, I've never done that, but it makes sense if you added the issues to the sprint, started it, and then adjusted the time back to a point before you added the issues. The chart is looking at the start date/time of the sprint, of course, but I'm not sure I would have expected it to recalculate the burn when you…
-
Jira doesn't do field-level security (apart from due-date, assignee and reporter) - either you can edit the issue or you can not. The only way to do this without apps is to move the edit into the workflow: * Remove the protected field from the edit screen, so no-one can edit it * Create a new screen with the field on it *…
-
The error message suggests that one of your custom fields is being provided by BigPicture and it is not able to handle the data you are trying to put into it. Could you check if one (or more) of the five custom fields is a Big Picture field?
-
Team managed projects do not have issue level security, so I think that may be a non-starter for you. For both team and company managed projects though, the key is who you let into the project. Team managed projects have simple roles, and the way to prevent someone seeing the project is to not add them to it. Company…
-
What app or process are you using to do this "signature"?
-
To limit the complexity, limit the number of cards in a column.
-
Welcome to the Atlassian Community! Um, actually, it's working fine. You do have a guideline in your diagram - it's the grey line running along the x-axis. This has happened because you started the sprint (which sets the estimate for the sprint) before you had any issues in it. You then added issues into the sprint, which…
-
I strongly recommend that you don't look at the database at all, For this particular query, you'd need to join 8 tables and do some parsing of one of the fields to enable the join. Just don't look at a Jira database, it's the worst possible way to report on Jira data. You can easily see unused status from the UI - go to…
-
Welcome to the Atlassian Community! All attachments are visible on a page, if the person looking has permission to see the page. I think you mean "does the page include a 'show attachment' macro/function so the attachment is partially or fully rendered when viewing the page". It is a technical quibble on the wording, but…
-
All bulk-edit does when you use it is run through the list of selected issues and run the same code that would be run if you have gone to the issue and clicked for the same change. All issue update processes re-index the issue affected, including delete issue. (The exceptions are field re-configuration, as issues are not…
-
No, there's no way to automate moving issues. Even with the advanced scripting or automation apps, it's really really hard. This is because moving issues between projects (or even issue types) is not a simple procedure. All the configuration is determined by the project and issue type, so when you move, you have to check…
-
"Template" is an accurate word to describe what Confluence templates do. A template provides something in a certain shape when you are creating a new thing. You can't apply templates to existing pages, because that's not what they are for. If you could apply a template to an existing page, all it could do is destroy all…
-
Welcome to the Atlassian Community! They're not being resolved on reports of incidents, they're being resolved on open incidents. Atlassian knows your site is broken, and have an incident logged for it. But to get you notified, I've asked Atlassian to get you on the list of people to be updated directly.
-
Yes, that's how it should (and does) work - you're adding a load of users to the system, and the licences are based on the number of users.
-
No, it looks like my previous answer was right, because no-one has given us any information that it is anything else.
-
What type of field is not appearing, and do you already have them on the screen? If " they do appear in the issues and all" then why are you trying to add them again?
-
Please keep referring to the status page, there's nothing more the community can tell you.
-
There are samples in the documentation and over at https://library.adaptavist.com