Nic Brough -Adaptavist- Expert

Hi Niki, welcome to the community I've seen you've posted a couple of similar questions before, and I'd like to apologise for not picking them up. As an explanation (not an excuse though), the community sees a lot of traffic and I think there's a lot of "I'm not sure, so I'll hope someone else who is more sure picks it up,…

Again, spot on, almost. If you'd said "remove 'any logged in user' and let the desired users in some other way", it would be 100%. The "almost" is not because "add a group" is wrong, it's absolutely correct, but there is another option you might consider. I default to using project roles instead of groups. With a group,…

I do, I suspect the apps you are looking at would be really helpful! So good luck!

Have you checked both the field configuration and the custom field definition?

Ok, there's a "field configuration scheme" for the project which is what you see first when you click into field configurations from the project. This should be a list of issue types (possibly only one - there's always a "default") mapped to different "field configuration"s. You need to ensure you are using different field…

That suggests you're using a field configuration for the "different" issue type that has the mandatory flag set. It may even be shared with the first issue type.

If you delete a label, it will be removed from all the cards, but there will be a line in the issue history to say it was applied and then removed.

Ah, ok, I see. This happens because the layout is formatting, done by the page it is on, the include is not bringing all of it in. Which is annoying. I think the only thing you could do is split the page into two pages so that the upper table and lower pair are included from different pages.

Odd, but it *might* be down to a controlled priority. Can you try renaming the priority and seeing if you can then enable it?

Yes, you're absolutely right. If you want different permissions for different projects, you'll need a new scheme to associate with the protected project(s) You can do them from scratch, but I prefer copying an existing one and then tweaking it.

Atlassian are gradually removing the ability to inject breaking javascript into descriptions. You'll quite simply have to remove the script from there.

For this sort of support or help, you probably need to engage one of the (training or consulting) partners - https://partnerdirectory.atlassian.com As for the question summary though - columns are collections of status. A move of a card from one column to another is actually a transition from one status to another.…

That's the problem then - you've set it up for the reporter to be emailed when "issue resolved" is fired, but you're not firing it in the transition. Change the transition so it fires the "issue resolved" event.

It's all of those things, potentially. You can't restrict people in Jira, the permissions are totally permissive. To hide a project from someone, you have to remove their access to it. Start with the permission scheme for the project and look at the "browse" permissions - those define who can see a project, You may find…

Welcome to the community. How are you telling Jira who the owner of a company is?

There is no issue or bug here. Jira has always defined at the last column on a board as "done". That's how boards work.

Ok, and does the "close issue" transition fire the "issue resolved" event?

If you remove the edit permission, the edit button goes away completely. There's nothing to click to trigger the pop up. I don't think you have a problem here.

Code - you'll need to inject code into the core of Jira so that it triggers your pop-up instead of taking people to the edit screen. I would recommend not bother to do this though, because * code change like this renders you unsupported * humans don't like pop-ups, they get in the way and irritate us It would be better to…

You propably need to get the reporter added to the notification scheme for the project (literally the reporter, not an individual) You will need to check the workflow to see what event is fired by the "close issue" transition, so you can match it up in the notification scheme.

What do you mean by "unable to enable"? Could you describe the exact symptoms?

You do not need to make a workflow active directly or "publish" it, the active/inactive display is not a flag, it is simply an indicator of whether the workflow is in use or not. To use the workflow without affecting existing projects, create a new workflow scheme (or, probably easier and quicker, copy an existing one that…

It's not a search I'm proud of, as it's really not that clever and it's not a "full" search. But one of "issuetype in subTaskIssueType()" and "issuetype in standardIssueType()" ought to be built into the quickfilters on boards - I'd say 1/3 of my Jira clients find one of them very useful.

When Hipchat was ended, some people who needed a server install simply went back to IRC, but a lot of people looked to https://mattermost.com for options. I've worked with it a little bit, it talks to Jira and Confluence quite happily. I quite like it, but I do think it's got some quirks that might put some people off.

You will need to code for this new functionality. I'm not sure you can add a function t automation with a an app, but you could replicate all of what it is doing and include your mapping code in an app, replacing the automation. Or use one of the scripting apps (obviously, I'd use Scriptrunner here)

The include macro only takes the content from the source page, as though it is part of the current page, which means it will take on the formatting and layout applied to the space and page within which it is being diesplated. Whatever you've used to change the portrait/landscape layout in space A will need to be applied to…

Yep, we have a handful of them in separate projects - it's mainly to make sure our automations lead to clear reporting that stop people having to ask questions about what individuals are up to. For example, our consultants have a wide range of clients and non-client work too. Obviously we need to report time worked for…

It's not unsolved at all, there was nothing to fix in the original report, it was the poster not quite seeing what it was doing. The secondary "can't add outgoing transitions to status that don't already have them in draft mode" bug was fixed in Jira 7.something. (7.6 from memory)

That would be a bug in Kaspersky's password manager, the only work-around currently is to turn the password manager off for your Atlassian site.

Properties are not a field, you can't use the field api to get them. I'm afraid the properties call on each individual issue you are making is the only way to get them.