Nic Brough -Adaptavist- Expert

Because post-functions don't go on status, they are part of a transition. Try clicking on a transtion's arrow/line, rather than a step.

Those are not buttons, they are links. Could you explain why you think they are buttons?

Welcome to the Atlassian Community! If you add the "pie chart" gadget to a dashboard, you'll see that you can give it a filter (dynamic list of issues to report on) and a field to group by (location or department)

Welcome to the Atlassian Community! This error can happen when you use characters that the database you are using for Confluence cannot handle certain special characters (the poop emoji is the one I've seen cause this error). You will need to look at the logs to confirm this is the problem.

You need to verify that the filter the gadgets are using actually works (the easiest way to stop a filter working like this is to build it to use a field that you then remove or rename, but there are other ways to break them) Look at the filter the gadgets are configured to use, then go to filters -> view all filters, and…

Try clicking the "board" option in the menu, it should give you "create board" as one of the options.

Could you describe what is actually happening here? In your first screenshot, you are starting to enter a field name as part of a JQL query, so I assume you're going for something like "issueype in (bug, feature)", but you don't tell us what "it won't let me add it" is. In your second screenshot, the message is clear - the…

Bother! Sorry about that, I mixed your post up with a "database problems with Jira" I was answering around the same time. Thank you for translating it into what I was asking for in Confluence, and answering the question I was trying to ask! This version of Confluence runs (supported) on MS-SQL 2017 and Azure SQL, so we can…

Welcome to the Community! Files saved where? What function are you using?

Or a new project, with a different key.

This is what it says it is - the database you have configured is reporting that it is of a version not compatible with this what is in your dbconfig file. You'll need to correct the dbconfig file, or change the database to a supported one.

What database are you using? Azure-sql does not tell us what type of database it is, and the errors you are getting look like you have chosen an unsupported one. Also, could you show us what you have in <jira home>/dbconfig.xml - it might be that you are using a supported database, but your connection settings in there are…

Welcome to the Atlassian Community! You are right to be reaching for a new field for this. Jira does not have any functions for grouping any of its recorded dates together.. Of course, I would script it, rather than use a field and ask people to enter it. A script or automation could easily populate a select list field…

Have you added any stories to the Epic? (Or issues of any type at the story level)

On a technical point - there's a howling design flaw in Jira in that you can not move issues from a status in a column to another status in the same column. Much as I am an Atlassian fan-boy, I won't defend that failure. > what is the point of having multiple statuses if you just group them into the three types? Good…

>This would generate a board with 11 statuses. This also have two starting statuses and two complete statuses, one for each workflow. No, it does not. It sounds like you have not actually created a board in Jira to cover this scenario. If you had, I would have expected you to have talked about the default columns you get…

Which Azure database are you running? Jira only works with Postgres, Oracle, MySQL and MS-SQL, but Azure can support all of them, so I'm questioning which one you mean by "Azure SQL"

>I take it you have not seen the new issue view? Been working with it since it arrived. Heck, I saw it before it went out to customers in general (and gave some feedback on the prototype, a lot of which was ignored) So what if a team can re-arrange their view of an issue? What's the problem with that? That's how they…

>Two workflows still means that you need two boards or a shared set of statuses. Why? I can't see any reason to need two boards or total alignment of status across workflows. Could you explain why you think you need that? Though that makes think further into how you might be thinking, leading to the question: What do you…

>Every project can override the view of the issues, I'm sorry, I still don't understand what you mean with "override". Every project has settings that determine how the project works. That's the point of projects - a collection of issues that have something in common, including a view. >So while you define what fields each…

I wouldn't do that. It sounds like it should be one project, but two workflows (which means two different issue types in that project) If you have them in the same project, you can share things like components and versions, but still handle them with separate boards if you want to.

Yes, there are a number of changes. You should not be worrying about them - your Tableau connection should be via the REST API which abstracts the data structures away from the database, and has not really changed since Jira 6.3 (it has changed a lot really, but the changes are all additive - REST calls that worked for…

"epic link = <name/key of Epic" will do it.

Eh? I'm sorry, I do not understand any of that. "company managed projects are overridden by boards"? What? What does that mean? What is being overridden? "data no longer can flow between multiple projects" - what data flow has stopped? Where? What is stopping the data flow?

Another option is to create your own "my work" dashboards - there are all sorts of gadgets you can add and customise for them. The most obvious one is a simple "filter list" - define a filter like "assignee = currentUser() and resolution is empty order by project", save it, and use it in a filter view gadget.

Welcome to the Atlassian Community! >The tasks are already finished in the sprints and are in the backlog Your board configuration is broken. A finished task should not appear in the backlog (boards in Jira usually refer to this as "done"). By definition, a backlog is a list of things that need some attention. If something…

I'm sorry, but this is wrong! It will indeed "hide" the done issues, but it also breaks all your reporting and board views. It completely stops you from doing Scrum or Kanban.

Welcome to the Atlassian Community! Yes, there are lots of us here. The best way to start a conversation here in the community is to ask a question on a topic, a general "hey, want to talk about something?" call doesn't tend to get much response.

I've run into this too, I managed to get away with swapping the database to read-committed. If I were you, I would test that change to read-committed works

It went to the email address on the Atlassian account the person tried to log into id.atlassian.com with - the one you are trying to re-invite. What level of subscription do you have? If it is standard or above (11+ licenced users), then you can raise this with Atlassian directly at https://support.atlassian.com/contact .…