Nic Brough -Adaptavist- Expert

Jira has a permissive approach to default permissions, and you will sort of need to undo that. Have a look at the permission schemes - each one of these has a line in it telling Jira who can see the project. This, by default, will be "any logged in user". You will probably want to remove that and replace it with another…

Um, clicking "simplified workflow" has nothing to do with editing your workflow. If you really do want to use a simplified workflow, then you'll need to rename the existing scheme to something else before simplifying again.

There is a third option, yes, you can write importers. On server, it used to have a pile of off-the-shelf importers for legacy systems such as bugzilla and redmine, and it was (and still is) possible to write your own (I helped one place write one for Remedy as that needed to be taken out and put out of our misery as fast…

The quickest one to fix is mapping "development" into the right column on the board, so people can start moving through the workflow, it'll take only a minute to pop in and do that. The rest of it is, yes, editing the workflow. Before throwing yourself into it, have a think about exactly how you want it to work. Do you…

Ok, so test it.

I assume by this, you mean you have run an upgrade, Jira is now running, but when you try to log in, you get some form of error? Is that right? On the rest of the question: These two are files that you had customised in your old installation. The installer/upgrade program has no way to know what you might have done in them…

Quick filters are for drilling down on a board - they let you remove things from the board view to enable you to focus on things. They do not add issues to a board, they can't because the board is supposed to only show the issues defined by the board filter, and adding random issues to a board would simply break it. For an…

Thanks for clarifying my misunderstandings! Yes, that does mean the services will stop being there, you won't be able to use them from Jan 1st next year.

If the project is "private", the first debugging question is "can the user trying the filter see the issues in the project at all?"

The dashboard is definitely the right place to be doing this, and I think you are pretty close already. With a dashboard (well, any reporting really), you need to be thinking of two things - "what issues am I interested in reporting on?", and then "what do I want to see about them?" The most obvious gadget for you given…

You would need to set up a series of filters to catch this, assuming your story points is a standard number field, so: * story points = 1 * story points = 2 * story points = 3 * story points = 5 * story points = 8 * story points = 13 * story points = 21 * story points = 34 * story points = 55 * And then I'd add an…

A dashboard is a collection of gadgets that show you information about your issues. Most of the gadgets are driven by filters that find issues to report on. Some filters are defined by the gadgets internally, based on the configuration you set for them, but a lot of the gadgets use filters you define and save for them. So,…

If the project is "private", the first debugging question is "can the user trying the filter see the issues in the project at all?"

Ok, then the second screenshot of the team-managed project is irrelevant. Your problem is that the new issue view tries to stop you making the mistake of putting the resolution on the create or edit screen, by simply supressing it if you do. There's nothing wrong here, you should see the resolution appear when it is set by…

Hang on, your screenshots are of the field/screen configuration for the different management styles for projects. Screens and field-configurations are used by company-managed projects, and field layouts by team-managed projects. Could you confirm which management type your project is using?

The most simple way to test an app is to try using one of its functions. Is "test it is working" what you really mean when you say "check"? I suspect you might be meaning something different?

Thank you, that answers my questions. You will need to find an app or do some coding to do this, probably in two parts. One part will need to be something that enables Jira to read the "VIP" property from your Active Directory. The second, which is harder, is going to need to do some form of highlighting of something when…

Welcome to the Community! No, there's no field type like Component, it's a single system field with load of functionality layered over it. The closest you can get would be to ask your admins to add a "Multi-select list" into the system and associate it with your project(s). These are similar to components in that you can…

Ok, the diagram shows that you do not have transitions between most status. As you say "no conditions, only post functions (5 is standard for an uncustomised transition)", let's ignore them. Your workflow has transitions Create -> Backlog -> Analysis -> Development -> Testing -> UAT -> Done Mostly a completely one-way…

The scripts are not kept in the context, they apply for the entire field. You will need to create a new field for each different script.

Still won't work, you'll end up with reports telling you different things.

This is not a "pre-defined" function, it has been added by the Power-Scripts app, and I don't think it does what you think it is. Have a look through the docs at https://confluence.cprime.io/display/JJUPIN/Pre-defined+JQL+functions#PredefinedJQLfunctions-issuesInFeatures to confirm that.

Performance - not a problem, unless you decide you're going to let people run riot with adding all sorts of custom stuff that they don't really need. If you're going to do that though, screens are way down on the list of problems you'll have with performance. Not using the standard one is not a direct problem, you'll just…

Welcome to the Community. Jira Cloud will not work behind a simple proxy like that. Not properly anyway. All your integrations will be using the Cloud url. All communications with it will not use your proxy (emails etc, will refer to the Cloud, not your proxy). Gadgets and reports will fail in interesting ways. People…

Simple approach is that you estimate time on issues (usually stories) and then log time when working on them. I think there may be more to your question here though. روش ساده این است که شما زمان را در مورد مسائل (معمولا داستان ها) تخمین می زنید و سپس هنگام کار روی آنها زمان را ثبت می کنید. من فکر می کنم ممکن است سوال شما…

The benefit is probably simply "standardisation, it'll work the same for everything", the disadvantage is probably "it doesn't do what this team needs". I don't think this question really works when framed as "advantage / disadvantage" or "pros and cons". I think there's another question behind it, but I do not want to…

Could you tell us more about "cannot download"? What are the symptoms? I can click on the link and end up with a (working) install binary on my computer, so without knowing the errors or feedback messages, I can't really help.

There are three types of Bitbucket service you might be talking about here, and the pipelines question is unclear, so I'd like to ask for some clarification. Note that bitbucket-pipelines is distinct from other software's pipelines and part of my confusion is likely to be that I'm not sure which pipelines we are…

You don't even need automation. Run a filter for whatever it is that identifies someone as a participant and other bits you might need. A typical JQL for this might be Resolution is empty and (Assignee = currentUser() or Reporter = currentUser() ) Save the filter, then go to "Subscriptions" for it. Anyone subscribed to…

No and yes. Let's say you put in: * Story 4 hours * Sub-task A: 2h * Sub-task B: 1h Here, your sprint estimate is 4h, because Jira does not look at sub-tasks. But the time that non-sprint functions look at is 7h when you're counting roll-ups. If you then implement "add up sub-task estimates to parent", you end up with a…