Nic Brough -Adaptavist- Expert

During my lifetime, the UK has been through a couple of periods where crisp (chips in American English) manufacturers try out all sorts of strange flavours. You can always find salt and vinegar, cheese and onion, prawn cocktail (which I think is an odd flavour in itself), barbeque styles, smoky bacon, and other obvious…

This sounds like your people are using very simple logging and understanding that they should be logging by day rather than week. For a week's work for me, I log 8 hours per working day. In my case, I'm usually jumping around across many things, but sometimes, I do a full week of project work. So, that should be 40 hours a…

I am not sure I understand what you are trying to do here. The way I read it is: If a user is assigned issue X then they are not allowed to do a transition on issue Y. Is that right? It's quite an unusual requirement, I would expect something more like "only the assignee of Y can transition Y" I can't tell why your code…

I don't think Atlassian will say much different. "Don't host illegal content in our products" is not something you really need to write into a contract or agreement. But, of course, I can't speak for them. I suspect they'd recommend a local lawyer, but I don't think the question is localised to Atlassian stuff - it's a…

I am not familiar with Float, but if you can do some scripting/coding in Float, then the easiest thing to do would be some code that does "when work is logged in Float, poke it into Jira over the Jira REST API" I don't know what you've tried with Zapier, but it's likely to be that sort of coding. I think I'd be looking at…

I am sorry, but repeating "by label" does not explain it for me. Please could you tell me either: * You want to report on a list of issues that have a specific label on them * If that is not the case, what does "by label" mean?

I am sorry, but "by label" still does not make any sense. Do you mean "a chart that shows me a report about a set of Epics that are identified by a label"?

Start at https://support.atlassian.com/jira-cloud-administration/docs/work-with-issue-workflows/

I don't think it's a work-around or fix for anything here, but you've got two options. Either start running the Jira system that you've configured for Bitbucket to use for the users, or re-configure Bitbucket to use another one. As you can't log in as an admin, it's likely that you'll need to recover admin access, with…

The user macros stop working, because they're not there on Cloud. You'll get a placeholder note saying "unknown macro" on view, and when you edit the page, you'll be able to see which macro is missing and all the content that was in there on the server page. By content, I mean any of your text/data that you've placed…

There's some slightly confusing use of language in this area in Jira. The "simplified" flag is not actually on the workflows, it is effectively held at a board level. When you simplify a workflow from the board options, Jira looks at the current setup of the board for the list of status and creates a new workflow (named…

Almost. See https://support.atlassian.com/security-and-access-policies/docs/understand-atlassian-access/ for the list of what it can manage

Ok, that's nothing to do with the board, the status are part of the workflow. You need to edit the workflow, removing (or hiding with conditions) the transitions to the status you don't want that go out from the current status.

I am a little confused. Description, Security level, created and updated are all system fields, they do not have contexts. Created and updated do not have default values either, they're set and updated by creating and updating Jira. Custom fields do have contexts, and some accept default values. The contexts are all set in…

If Dynamics requires those _#_# codes from Jira in order to work, then there is nothing you can do - removing them is going to break your integration. If it does not need them, then go to Admin -> Issues > Custom fields, find Product Group L1, configure it, and edit all the option names down to what you want.

> can we update/Migrate our Source Jira Server(Hosted on VMWARE) into a signal node Jira Datacenter without changing the hardware/platform, if yes then what will be step for the same Check your apps are all compatible first, and if they are, apply a DC licence to it. >can we migrate our source Jira server to single node…

There's no way to do this directly from the labels, but you could look at automation or scripting. My initial thought would be to have something that can read all the labels being added and set a group-picker field which can then be used by a security scheme to hide issues. (Or just set the group-picker field and forget…

What do you want from this "integration", what is it going to do? What are you actually trying to achieve?

Just search for Jira or Confluence fora. You won't get a lot of "live chat" from them, people are all still volunteers like they are here, and I tend to stay off them because I don't have time or will to filter all the terrible advice/answers out from the good stuff you find there. Best place to ask questions is of the 3.5…

That does not change the fact that you should not be touching the database. As soon as you do it, you have lost support, and you have no way of knowing what you may have damaged. Even if you've done it properly (stop Jira, take a full backup, restore and prove that somewhere, make your changes, restart and run a full…

There are a load of places you can ask for help, some of them chat based, but The most expert people are Atlassian and this Community, and for official support, you need to engage with Atlassian or a partner.

That's nothing to do with the question.

This is something you would need to ask of a lawyer, not people here to talk Atlassian tech. Generally, I would default to assuming that it is illegal because everything is effectively copyright protected and hence you shouldn't be taking it without the owners consent. Linking to public documents is fine, copying them…

There is nothing wrong with what you are trying to do, just the way you are trying to do it is utterly wrong. Let's go back to the original statement (I have shortened this to simplify it: * [I] wish to force attachment whenever a new feature is moved to development * (since validators won't perform best) * Add [something…

Ok, I didn't realise they'd added this note. I suspect it is accurate, but refers only to apps that have been able to be get access to the back end, which means a very specific and limited set of apps that go via Atlassian. I Forge enables the creation of new custom field types, but I am not sure it can inject types that…

Validators are not "better", they're the right way to do it. Post-functions are not the place to do validation.

You can't. When you deleted the field, you really did delete it - all the data for it has been deleted.

And in 3 months time when something fails because you damaged your data? Stop it. It's the wrong thing to do.

One of your administrators deleted the custom field that was being used by the board as the estimation statistic - the 10131 you see displayed was the unique id for the custom field in the database. You can't "revert" as the field has been completely destroyed, but you can just select another field for the statistic. Story…

Your server cannot reach the database you have set up for it. You will need to debug that connection. Start with a look at the Jira application log, it should give you a bit more detail about the actual error, including whether it simply can't reach it at all, or if it can reach it but the database is giving it an error…