Comments
-
I may be missing your point here. JSD agents will not and should not show under Customers. They will however show under project settings > people.
-
What do you mean by a group? Can you explain and/or share screenshot if relevant?
-
Yes they can. You can check addons at marketplace.atlassian.com you would want to start with Jira Software as the product from Atlassian.
-
I would use a business project and make use of Components field to differentiate your clients.
-
If you are on cloud it is possible that a recent change has introduced an unintended behavior. The other thought is that this is caused by an addon. I would review the latter and then consider reaching out to Atlassian Support. One question- is it only two users experiencing this?
-
No you can’t do that. While you can have a task sum up the estimations of sub-tasks, linking does not provide the same feature. You could consider an addon and scripting.
-
Ah, I see. I was thinking you were saying the user was showing in the drop down for selection of Assignee. I do not believe you will be able to eliminate those names at least cleanly. I have found that trying to delete users rather than simply making them inactive to be fraught with errors.
-
Hi Amaresh! I have used JSD for staffing which covers search, interviewing, offer, etc. then I have used JSW for the Onboarding actions. Happy to chat if you think it would be useful.
-
Have you inspected one of the workflows where the transitions lead to Done to ensure that indeed there is a screen associated requiring Resolution?
-
You need to ensure they are not customers in the project. Go to the project in question and select Customers. If you see the agent(s) listed there or under any Organizations then remove them.
-
If the user show in the “no site access” list under Jira settings > User management then they should not show in the drop down for Assignee. Please verify this is the case.
-
It sure sounds like someone has changed your workflow and renamed the Open status. Can you check the workflow for one of the projects that are showing RDY?
-
issues of type sub-task should not show under any 'create issue' screen. Sub-tasks are created from the detailed issue view of an existing task/story. Given you are receiving two conflicting errors I have to wonder if you have two issuetypes named "Design Bug", one as a task and one as a sub-task. Referencing your first…
-
There isn’t a field that will tell you ‘updated-by’. To know that you would need to look at the detail issue view and History. You could add “Updated” field which iwill display the date an issue was last updated. You might check addons for the desired functionality.
-
I don’t know any way to achieve this. Automation happens ‘after the fact’ so that won’t work.
-
Thanks for running this to ground Daniel!
-
Ah ok. Attachments must be accessed via the portal. They are not attached to email notifications. Customers would need to click on the link in the email which takes them to the portal where the attachment can be viewed.
-
What type of user are these clients, Customers or Agents? Where are they attempting to access, portal or application? Cloud or server? Do you have any addons and if so please check that they are current.
-
There are only the two reports currently available for NG projects.
-
My first question is whether you are using Jira Software (JSW) or Jira Service Desk (JSD). The reason I ask is that you have opened this in the Jira collection but you mention queues and customers which are typically JSD terms. Regardless here is so,e input that might help you as you grow into the Atlassian portfolio. * In…
-
Position?? Please explain what you mean.
-
Just add the following to your Kanban filter. ...and fixVersion in unreleasedversions() there are other options you may wish to consider, e.g. add a sub-filter to not include issues resolved more than say 7d prior.
-
You need to set up an SLA and use Automation for when it breaches. If you need assistance this LMK or check the documentation on setting up SLAs and Automation.
-
The ability to customize the portal Is quite limited OOTB. I recommend searching the Marketplace. You can also search the Community here to see what others have discussed on this topic.
-
How do you wish to display this? Do you want a filter list or something else? A simple solution is to use the Filter List gadget and simply add the Epic field to the columns. Depending on your requirements you could simply use the project for the filter or create a filter e.g. project = abc and issuetype = story and “epic…
-
When manually exporting issue in the search issues view there are two options for CSV export: all fields and displayed fields. Create your search filter, set the columns to display the fields you wish to export and choose the export displayed fields option.
-
Yes you can remove them from an Organization without issue.
-
Agree and it is worth noting that a user isn’t really “opening” an issue but simply viewing it. The subtle difference here is that viewing isn’t an event that can be used to trigger any action. You need a transition to trigger an action.
-
This is a frequently asked question in the Community so you will find much discussion on it here. Here is a quick summary. * you can not customize the columns in the portal at least OOTB * check Marketplace for addons that allow portal customization * there is at least one open suggestion with Atlassian to allow for this…
-
Neeta, sorry for the delay. I am in the middle of moving and not online much throughout the day. So first, unless something has changed any user should be able to create a dashboard. The global share permission gives a user the ability to share the dashboard or other object. To be clear, is this the only user experiencing…