Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

  •  
     
    story #13573 See at a glance which parts need configuration
Actions
Summary
Newcomer Tracker administrator
See at a glance which parts need configuration
I am guided a little and I go first to pages that are usually in need of configuration, such as Fields usage, Semantics, Permissions, Workflow.
I don't waste time in CSV import, Canned responses and other menus that are more rarely used.

This is a follow-up of story #13570 Navigate in tracker administration with tabs

The "pulse" information is stored per-tracker. Once a tracker administrator visits a "pulse" page, the visit is stored and the "pulse" is no longer shown to others.
The pages that have a "pulse" are not configurable: it will always be "Fields usage", "Semantics, etc.

See mockup in Figma: https://www.figma.com/proto/RaBL0FL199pbWkh7TUJXIrAP/Trackers-service-flow?node-id=39%3A492&scaling=scale-down&redirected=1

Empty
Empty
Status
Empty
Ready (stalled)
Development
  • [x] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#13573
Joris MASSON (jmasson)
2019-07-01 10:44
2019-07-01 10:44
14753

References
Referencing story #13573

Artifact Tracker v5

story #13570 Navigate in tracker administration with tabs
epic #2047 Tracker
Referenced by story #13573

Artifact Tracker v5

story #13570 Navigate in tracker administration with tabs