Comments
-
Welcome to the Atlassian Community! There is a strong argument that Atlassian are trying to monetize their products as much as possible. If Jira Work Manangement provided the same flexibility that Jira Software requires (like the power to use saved searches to drive a board), then there would be no need for anyone to buy…
-
Yep, Jira Software absolutely does have the "concept of resolved", it's the same as all the other Jira products - you need to set a resolution for Jira to see an issue as resolved. Jira Software's boards do have a different slant - they need an issue to be in the last column for them to consider an issue "done" (which is…
-
There is nowhere you can list the fields and see "system field", so I'm stuck on why you think the field is a system field and say you can see it listed as such. If it is a system field, then it will have a common name. If you can tell us what it is, then we can explain the way it is behaving (system fields have fixed…
-
The connection source is not the problem, you need to look at how your network is deciding to grant or block access.
-
Welcome to the Atlassian Community! I would set up a project, probably an ITSM based one, to contain all the change requests your people will raise.
-
I can't say I'm a fan of Las Vegas itself I'm an old, grumpy, antisocial, and introverted person with few taste buds (meaning, I'm happy to drink the cheap or free stuff - don't waste money on the better drinkies). I'm not a shopper, a gambler, eater, or much of a theatre visitor, so Las Vegas does not really have a lot to…
-
There is an option for "none" as a default value. Should be at the top of the list.
-
Ok, but what method are you using to create the links?
-
Could you show us that? I can't see inactive events when they are active, so I'm a bit stuck on what you are seeing.
-
So it is active. What makes you think it is inactive?
-
Welcome to the Atlassian Community! It depends on how you created the link. What method are you using?
-
And what about the rest of the answer?
-
Hi Kimberly, The short answer is "no" - the assignee field is the assignee, custom fields are not, so they can't have permissions applied to them.
-
Welcome to the Atlassian Community! Oddly, I'd actually say "none". You don't need academic qualifications to be an expert in Atlassian stuff, I think experience, the ability to think, and the soft human skills like listening and then questioning people (your end users mainly) are far more important. I have chosen to hire…
-
Welcome to the Atlassian Community! Nothing, all you need to do is click "create board". The publically available documentation covers it all as well, including the details of configuration.
-
This happens when all the workflows that fire the event are inactive, or there are none using it at all. You probably need to publish the draft workflow where you have added the event. A number of versions ago, there was a minor bug in Jira that meant you also have to have triggered the event at least once to get Jira to…
-
Welcome to the Atlassian Community! The "category" field in Jira is derived from the project and is only there for searching. You put projects into categories, and then you can search for issues with "category = X". It is not a field you enter directly on to issues, it's a function of the project.
-
Welcome to the Atlassian Community! Labels already de-duplicate themselves (try adding DOG and dog as a label), and the field offers existing label options. So I'm a bit unsure as to why you're asking for a label field that does what the label field already does. Could you explain a bit more? What is the built in label…
-
I strongly recommend that you do not do this. Deleting the sprint information on an issue destroys all the reporting on the sprints. To stop having issues move to the next sprint, you need to flag them as "done" before you close the current sprint.
-
Welcome to the Atlassian Community! Go to my.atlassian.com, find the system you want to subscribe to, and click on the purchasing options.
-
This sounds like your "system field" is actually a custom field, and one for which you have specified a context. A custom field context, for a select-list type field, contains the list of options. I suspect your context is different for the new project, and you've not added any options into the context. You should check…
-
Ok, so you can add a clause for "and issuetype != 'CP Patch Request'"
-
Welcome to the Atlassian Community! You'll need to move to the advanced search, where you can specify and and/or or operators to join search clauses.
-
This is what conditions are for, not validators. A condition is evaluated every time someone lands on an issue screen that might offer transitions to the user. They're simple true or false questions. When true, the transition is offered, and when false, it is removed from the options. A transition can have many conditions,…
-
That suggests that you are not logging in with an account that has administration rights.
-
How are you telling Jira that an issue is a "CPR issue"? Issue type? Project? Content of a field?
-
This is something you should configure with your networking tools, not the application. I'm not a network expert, but my first instinct would be a firewall rule on the server that blocks access along all routes you don't want to use.
-
You can do this by using workflow properties to change the permissions by status, but only for a couple of fields. The trick is to understand that the assignee field is controlled by permissions, unlike most others (most fields work off the "edit" permission, which is global - it affects the whole issue, not specific…
-
Yes, it has worked fine for me, with several clients. Where is it going wrong for you? Are you skipping parts of it?
-
The point of a burndown chart is to show you the velocity of the sprint. This is measured by the sprint estimates on the issues in the sprint and whether the issue is completed or not. There's no way to change how a burndown chart works, because it would not be a burndown chart if you drew it up from not done status or…