The issues is in the help center when they create a ticket they can see all the different clients. I currently have different projects setup for our clients. Modifying the screen allows you to add or remove a field once, and the changes will flow through all request types sharing the same issue screen. View only specific projects in help center based on user. Check the SHARED BY PROJECT link under Configure Screen to see what other service projects may be impacted. Note: Any changes you make to a screen may impact request types in other service projects that use that screen. Hover over any fields that you don’t want to display on the issue view, and select Remove. In the bottom right corner, select Make existing fields available. Select the request type you want to customize. Select a work category in the left hand navigation panel. Moving to Jira now offers us the opportunity to have projects based on the type of task. There are no workflows in Basecamp, it is fairly uncomplicated. To hide fields for every request type that uses the same screen:įrom your service project sidebar, select Project settings, and then Request types. We are moving over from Basecamp where we have traditionally managed projects based on the client with the various tasks in each client project. You must be a Jira admin to modify screens. For example, the request type Fix an account problem is a Service Request issue type that uses the Request Fulfilment View/Edit Screen. In your service projects, request types are associated with issue types that link to the relevant screens. Want to modify the issue view for all of the request types that share the same issue type Modify the issue view for a specific request type Learn more about configuring the issue view for a request type. These fields are configured under the Issue view tab, under Hidden when empty fields on the request type configuration page. Streamline your workflows from design to code with Atlassian. Now, fields are hidden under the Show more link unless values have been entered. From design to code: how Atlassian and Figma help designers and developers collaborate. In the previous issue view, fields weren’t shown unless they have a value. Show X more fieldsįields shown above the Show X more fields link are usually considered always-important, while fields nested under the link are considered sometimes-important. Now, fields are visible by default, regardless of whether or not they have a value.Ĭonfigure multi-line fields under the Issue view tab under Description fields on the request type configuration page. In the previous issue view, fields would only show when they have a value. Multi-line fields allow your agent to add more information to the request.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |