Nic Brough -Adaptavist- Expert

No, you can either see a space, or you can not.

The question is here is quite simple - is there one story here or two? If there's two stories (one for FE, one for BE), it's simple, there's two stories, so you split the issue into two. If there's only one story but it has two parts to handle separately, then create a sub-task for each. There are three logical situations…

Your question is not clear. What does "cannot reach" mean? What are the symptoms of the problem? What are the error messages you see whenever you try to "reach" it?

The user does not have "assignable user" permission. This will be because they either are a disabled account, or the permission scheme does not include them in the rules for assignable user (note - not assign issue, it must be assignable user)

It's not logged in Jira itself, but if you're using an external directory of some sort, it is probably logged in there.

You could just put the resolution field on the "create" screen for the issue type. This would mean anyone creating an issue will fill it in (the resolution field doesn't have an empty option to offer, it always gets set when it is on a screen) With that, you could have a workflow that's just O -> Closed (Meaning no actual…

Your requirement directly contradicts itself when you say "... a user who does not have the Browse project permission ... user to be able to see only the tickets and update that he has created" Do you want them to be able to see the issue or not? I'm going to assume that you do want them to be able to see the issue. The…

You don't need apps or complex configuration to do this, Jira does it off-the-shelf. Every transition in your workflow has a post-function that says "fire event: x" The project has a notification scheme that says "email these people when that event happens" (people named individually, or by group, project role, dynamic…

You can not just set the status, it is not a field. Status is an indicator of where an item is in its workflow. To change the status of an issue, you must tell Jira to transition it from one status to another.

What do you think a "solution" would do? This warning is simply telling you why the list of issue types is shorter than you might expect - you can't swap between types that are configured differently on this screen.

The Community is based on Khoros, not Confluence, so there's not a lot of people who can help here. If you were to use Khoros to do it, then it's probably worth looking in the Khoros community!

There is no "two way" transition, you have to create two of them, one in each direction. What made you think you could have a single bi-directional transition? If it's the double-ended transition lines in the diagrams, they happen when the steps have an incoming and outgoing transition anchored to the same point on the…

The previous incarnation of this Atlassian Community was actually built on Confluence + Questions for Confluence - it is very much aimed at the question/answer/follow-up cycle though. For something a bit more forum like, see https://marketplace.atlassian.com/search?product=confluence&query=forum - some are directly forums,…

There's a few problems with this idea, and actually, Jira doesn't work this way at all. Each security level for an issue is actually a rule that says who can see the issues with that level on it. This means you can do things like: * Top Secret: Only the user called Bob can see these * Secret Squirrel: People in the role of…

Oh, well spotted! I imagine that could be really hard to find buried in two similar applications!

I'm not your Confluence admin! I can't do any of this! You might find it easiest to log in as an admin though, you can go to Admin -> General config -> Troubleshooting and support tools -> Get help, and there's a little wizard that will run you through creating the call Whichever way you want to do it, creating a call…

Jira does not automatically shut down or restart after re-indexing, it doesn't need to. Also, I want to question why you ran the re-indexing? Some people think running a re-index speeds up the system for them, and start doing it on a schedule, especially when they are perceiving Jira gradually running more slowly. The…

This is a bit stronger with Jira Software than Jira Service Management, but when I said "narrow ranges of compatibility" before, it's entirely possible that you are currently on a version of Jira Software that is the only match for your current version of Core! From memory, if you have, for example, Jira Core 8.19.0 then…

Ohh, hang on, you say "The field type is a view-only message." There are three things you might mean as a field type: * Read-only field. These can only be set by code, and by definition, won't appear on the create screen, because they won't have any data to show until after you've created the issue. They won't show on…

Yes. Probably Given we don't know what you mean by EDC or what you're really trying to do, we're not the best people to answer the partial questions. Rather than asking lots of disparate out-of-context questions about what Jira may or may not support in your field, it's probably worth you reading Atlassian docs about what…

Please see the answered thread above, which explains how Atlassian gather interest.

It won't, Atlassian don't use Community for gathering requests - see my previous comment.

I'd want to generate the support/troubleshooting support file and raise it over at https://support.atlassian.com/contact

You mention CPU and memory here, which are important, but the indexing is also heavy on the disk. If you've got a slow read/write on your local disk where the index is stored, no amount of CPU or memory is going to help.

Welcome to the Community! Trello's main user account system is the Atlassian Account system. When you use that, you are "directly accessing Trello".

The workflow functions are the right place to look, but they might be falling over because of broken data or configuration change, rather than the functions themselves going wrong. The screenshot only contains the first part of the error, we need to look at the rest of the error, probably the last few lines that name the…

I don't think Atlassian mention the Σ fields enough in the docs! If you're reporting or exporting on time, they're really handy to add alongside their non-Σ partners when you've got anyone using sub-tasks.

Jira uses the sigma fields to add up time from sub-tasks - the "time tracking" "field" is actually a compound field, holding and accumulating quite a lot of data related to time-tracking. The obvious ones are that original estimate, time logged and remaining time are all part of it, they're not really separate fields. The…

Ok, so you're doing something really odd with your "access". Could you tell us exactly what you are doing when you try to "access" the service? If, for example, you are "opening the url in a browser", that's fine, but a browser will always give you an error message (unless you're opening the wrong url, one with no content…

Always worth checking! No, you're not missing anything!