Nic Brough -Adaptavist- Expert

Ok, great, not that then. Do you have "Edit" and "schedule" permission in the project?

Just to rule one thing out, is it ordered only by rank? Or are there other orders on it?

This is not strictly a "work around", it's "setting the workflows as intended". If you read the "repro steps", you'll see it's missing the actual association that is included in the "work around"

You won't get that. Atlassian support doesn't do that without going through all the debugging you can via the support request, and, we're not Atlassian support. If you could show us your configuration, we might be able to help. Start with screenshots of the permission scheme for the project and the "post functions" display…

Solved is the word Khoros (the community platform) currently uses as shorthand for "this question has been answered". We are not putting "Solved" on anything, we're providing answers. "Jira can't do that" is a perfectly valid answer, and so when someone accepts that as the answer, Khoros says "solved" Personally, I'd…

That's exactly what you do do. Go to the project settings and allow users in.

There are no apps that create group assignees - you can't change the way assignee works. But you can implement custom fields off-the-shelf for "other people who are involved" - as above, group-picker or multi-user-selects are what most people do when they need associates. JSD and Software can also use associates to the…

You don't need apps. On your Confluence page, type /jira and give it the issue key. Or filter if you want a list of issues. You can also insert the macro from the editor toolbar.

You'll need to explain the problem and what it has to do with Atlassian if you want any help here. Start with the Atlassian application you're using, what CPS means and what a 128 belt is.

Yes, but it's a bit of a pain to get to. Confluence has templates which are simply pages with pre-populated text on them. They're essentially the same as pages, but when you're editing a template, you have an additonal formatting option - you can flag content as "placeholder". When you use a template to create a page, if…

There's a scripted field that almost does what you want over at https://library.adaptavist.com/entity/calculate-the-difference-between-two-dates - shouldn't be too hard to convert from "calculate difference" to add X months to a base date and return it"

Check the conditions on the workflow, if it's the same workflow in another project, then there's probably a condition that says something like "only people in role X can use this transition", and you're in that role in the old project, but not the new!

This can be caused by one (or several of three broad things) * The connector is not compatible with your Jira * The connector has been compiled with a different version of Java, and is not compatible with the Java underneath your Jira * The connector has a bug I would check the release compatibility with the vendor's docs…

This is a networking problem, not a Jira one. It simply means that when your connector is trying to reach your Jira, the server is is running on cannot look up the name of the (Jira) server to connect to. You need to make your Jira server name resolvable on the server that is throwing that error.

What do you mean by "User Story" field? Is it a custom field, or do you mean something like the Issue Type? I assume by "lock" you mean "disallow changes" - there are ways to do that, but I'd need to know what the field actually is before I can start to describe what you'd need to do.

Project lead is not an issue field, it's a project attribute. You could add a field and then work out how to populate it on every issue creation event (and you'd need to think about how to bulk-edit it when the project lead changes)

Use the Jira macro to insert links to issues in a linked Jira system. You could also simply put in a standard web link, but the Jira macro is a bit more powerful.

No. Atlassian have closed them with "won't do"

It's the Epic report that does not make sense, not using Epics to group things. Remember the Epic report looks at estimates on cards, not throughput, which is how you measure Kanban. Jira's Kanban implementation is for doing Kanban. The Epic report is for doing Scrum (or non Scrum/Kanban stuff that looks at estimateS)

Welcome to the community! There are two times this can happen: * If you are on the free version of Confluence Cloud (although last time I looked at a free one, the tab was there, but greyed out with a note that it's not configurable on the free version) * If you have enabled "share page to non-users" - this is in general…

Are you writing an app for Confluence to do this, or is it a remote application that will use the REST API to poke the data in?

There is no movement to be made - you do not want multiple-assignees and Atlassian are not going to implement it, they closed all the requests with "won't do".

My guess would be that an inexperienced admin has put the resolution field on the create issue screen. You need to get it removed as soon as possible - whenever it is used on an "edit" activity (create, edit or transition), it will be defaulted and filled, hence making the issue resolved! Any value in that field means "the…

It's not far off. The easiest, and probably best, way to do this is include the "external" issues in your board, so there's no duplication, but if you can't do that (because it would mess with other people's numbers), then your idea of Clone and include is probably the next best option. One of the projects I'm on at the…

It's not clear how you are generating the table, so I'm not sure. Where is it coming from?

Do you have the anonymous access tab, and have you turned off the public links option in general config?

Start with something like: issue in linkedIssues(XYA-123,"is duplicated by") This will get you the issues. How they are displayed/listed is up to whatever you are listing them in.

Ah, ok. Well that macro simply redisplays the contents of a table. So remove the data that you don't want to see from the table, and the macro will render what you want.

How are you doing this in Confluence?

I'd guess you've made them all administrators - admins can delete projects.