Project

General

Profile

Task #3360

Feature #3318: Mercury UI improvements from ESIP feedback need to be addressed

Provide Member Node documentation on node naming best practices

Added by Chris Jones over 11 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2012-10-23
Due date:
% Done:

0%

Estimated time:
40.00 h
Story Points:
Sprint:

Description

Nodes shouldn't use acronyms or 'MN' in there names. be sure the documentation guidance says so.

History

#1 Updated by Chris Jones over 11 years ago

  • Target version changed from Sprint-2012.44-Block.6.2 to Sprint-2012.50-Block.6.4

#2 Updated by Dave Vieglais over 11 years ago

  • Estimated time set to 40.00
  • translation missing: en.field_remaining_hours set to 40.0

This is a member node administrator issue and there should be some policy on making the names as self explanatory as possible.

#3 Updated by Skye Roseboom over 11 years ago

  • Target version changed from Sprint-2012.50-Block.6.4 to 2013.10-Block.2.1

#4 Updated by Skye Roseboom over 11 years ago

  • Target version deleted (2013.10-Block.2.1)

#5 Updated by Dave Vieglais over 6 years ago

  • Status changed from New to Rejected

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)